> We don't currently expose an API to integrate custom block devices, although it could be possible.

I was thinking more about arbitrary custom devices, like custom network drivers (e.g. to connect to a server-side virtual network rather than tailscale) or custom filesystem drivers at either the block or FS layer.

> At this stage we believe that keeping CheerpX proprietary serves our growth plans the best, this could of course change over time as adoption increases and we build further added-value products on top.

I'd be very interested in chatting with you about our respective products' future plans.