Access infrastructure, not a walled garden
qbit.me doesn't generate your app for you and it doesn't host your code on someone else's cloud. Instead it gives you a clean path from a project folder on your own appliance to a public HTTPS URL — and gets out of the way.
You own the project. You write the code. You build it on your appliance over SSH. When you're ready, qbit opens a secure reverse tunnel to qbit Cloud, terminates TLS at the edge, and serves your app from *.apps.qbit.me — or your own domain on a Business plan.
Your project. Your hardware. Your web address. qbit handles the connection, the security, and the routing. You build the app.
How it works
1. Start the app from your dashboard
From the Applications page in your qbit dashboard, create a new app and pick the qbit agent it will live on. qbit creates an Application record and a project folder on that appliance. No code is generated — you start from a clean placeholder.
2. Build it on your appliance
SSH into your appliance and build the app yourself in the project folder. Angular, React, a static site, a single HTML file — whatever you want. qbit serves the folder, so the project structure is your call. Test it locally on your LAN as you go.
3. Publish when you're ready
When you want the app reachable from anywhere, click Publish in your dashboard. Your appliance opens a secure WebSocket reverse tunnel to qbit Cloud, and you get a clean web address:
your-app.apps.qbit.me
No router changes. No separate hosting account. No late-night DNS confusion. It just works.
4. Use your own domain (optional)
On a Business plan, you can publish apps under your own web address, like app.yourdomain.com. You point your domain at qbit Cloud, we verify it's yours, and we keep the secure connection current automatically.
What's included
- Project folder on your appliance: A clean workspace qbit creates and serves — no scaffold lock-in, no generated boilerplate
- Runs locally first: Test privately on your own network before going live
- One-click publish: Make the app reachable from anywhere with a single toggle
- Secure by default: Every published app gets an encrypted web address, restrictive permissions policy, and cross-origin isolation headers
- Self-healing tunnels: If the connection drops, the appliance re-establishes it automatically on the next sync
- Custom domains: Use your own branding on a Business plan
- Full lifecycle control: Archive, unarchive, publish, unpublish, or remove apps from your dashboard
- Privacy choices: Keep an app private, share it with select teams, or make it publicly available
Plans and limits
| Plan |
Published apps |
Custom domain |
| Personal |
Build locally only |
— |
| Professional |
Up to 10 |
— |
| Business |
Up to 50 |
Yes |
Free users can still build and run apps privately on their appliance. Publishing to a public web address requires a paid plan. Quotas count active, non-archived tunnels only.
Use cases
- Internal tools: Dashboards and workflows for your work, kept private to you
- Client portals: A place for your clients to log in and see their information, on your domain
- Landing pages: Launch campaign pages on a stable
*.apps.qbit.me address
- Agent interfaces: Web pages that let non-technical people use your agent's capabilities
- Shared team apps: Publish an app and share it with a specific team — only members see it