I hope you get in touch with @Christian_Schmitz or @Björn_Eiríksson they’re our resident plugin makers. Christian is quite good at wrapping existing libraries and functions quickly, albeit at the cost of design abstraction.
Christian / MBS Contact page
Björn / Einhugur Contact page
MBS has experience partnering with library makers for licensing.
I would urge you to reconsider your subscription-based licensing scheme. 
Welcome Kevin,
Well, if it helps.
@Geoff_Perlman is CEO of Xojo
@Christian_Schmitz is a popular 3rd Party plugin vendor MBS
And @Björn_Eiríksson another popular 3rd Party vendor Einhugur
Hopefully they’ll see your post. All the best!
Definitely, I’m more than open to make something custom here.
So far our sales have been direct to enterprises (the 21k price is precisely to help them navigate their internal purchasing flow with a one-off) but we have cheaper versions for smaller companies or shorter development needs. This would be the first time we’d offer SimpleBLE as part of a bundle of this sort, so it’s a learning experience for us as well.
Thanks for the link
Geoff just assigned someone to the Feature Request: Add Bluetooth to the Framework
Please have a look and add to the request.
Just sent a link to this thread. Is anything else needed?
In my case it would be for PICO - RASP PI(5). The Raspberry Pi Pico SDK now supports Bluetooth Classic and Bluetooth Low Energy (BLE) on the Raspberry Pi Pico W development platform
Using this article https://www.designnews.com/electronics/using-raspberry-pi-pico-w-for-a-bluetooth-low-energy-application
With the advent of version 1.5.1, the Raspberry Pi Pico SDK now supports Bluetooth Classic and Bluetooth Low Energy (BLE) on the Raspberry Pi Pico W development platform. As expected, following the announcement of Bluetooth support, a number of Pico Bluetooth examples based on a port of BlueKitchen’s BTstack became available.
The PicoW is a basic BLE hardware implementation consisting of a microcontroller overseeing the transmission and reception of Bluetooth radio traffic via a Bluetooth radio module. The microcontroller is governed by a Bluetooth stack; the inclusion of a Bluetooth stack allows the PicoW hardware to assume the role of client or server in a Bluetooth application.
For controlling end effectors (solenoids, SCRs etc) and developing on iOS or Droid this fits well with XOJO cross platform. For me XOJOs strength is a RAD with great UI capabilities. While that exists in other Dev Platforms XOJOs enables quicker development without loss of UI. The UI capabilities are great and making custom elements is also good. Having Bluetooth Classic and Bluetooth Low Energy (BLE) means all aspects can be developed on XOJO. No work arounds needed.
IMHO that is far more powerful than just the RaspPi piece as this now becomes complimentary. It becomes a win win opening the door to much more.
Great reply - yikes
Do you have examples for ARM 64 use?