Crypton BYOD helps teams turn Android phones into reliable SMS gateways — provisioned once, managed from a clear web dashboard, built for real operations.
Until now, that experience lived on crypton.sh. Many of you asked for the same product on your own servers: your URL, your data residency, your compliance boundary — without learning a different app or workflow.
You can do that starting today.
We’re releasing Crypton BYOD Platform 0.1 for self-hosting, alongside an updated Crypton Companion app that connects to the server you choose.
Same app. Your server.
If you already use Companion on crypton.sh, nothing fundamental changes on the phone:
- Same provisioning flow with a CRYPT-… code
- Same device management and messaging in the browser
- Same focus on security — encryption, recovery, and familiar account protections
What’s new is where the service runs. Point Companion at your HTTPS address instead of crypton.sh, complete setup on your instance, and you’re in business.
App updates still come from Crypton — so you stay on supported Companion releases even when BYOD runs on your infrastructure.
Why self-host?
Organizations choose self-hosting for different reasons. The common thread is control:
- Data stays closer to you — on hardware and networks you already trust
- Fit your policies — align with internal security, audit, and procurement requirements
- Your brand, your URL — operators and integrators see your domain, not a shared hosted endpoint
- Optional connection to Crypton — link your instance to crypton.sh later if you want notification email delivered through Crypton instead of running mail yourself
Self-hosting is not a stripped-down edition. It’s the operator experience we use on crypton.sh, packaged for your deployment.
What we’re shipping
Crypton BYOD Platform 0.1
A ready-to-run release for teams that want BYOD without depending on our hosted environment. Install with Docker, walk through a guided first-time setup, add devices, and go.
Companion update
Set your Server URL in the app when you provision or in Settings anytime. Built for production HTTPS; flexible enough for private networks when you need it.
Together, they answer a simple question: “Can we run Crypton BYOD ourselves?” — Yes.
How to get started
- Deploy BYOD Platform 0.1 on your infrastructure (HTTPS in production).
- Finish setup in the web UI and create your first device.
- Open Companion, enter your server address, and provision with your code.
Documentation and the container image are on GitLab. If you want help with licensing for redistribution or hosted offerings, reach us at [email protected].
Crypton BYOD Platform 0.1 is available under the Crypton Source Available License — self-host and adapt for your organization; contact us for commercial use beyond that.
