Mobile app is the keychain.
A key in the Secure Enclave (iOS) or the hardware-backed Keystore (Android) protects the only copy. Lose your device without cloud recovery and the data's gone, like a hardware wallet.
Your stuff, on your hardware, with a real green padlock.
Plug a small box in at home. Pair it with the mobile app on your device. Build and share services privately at yours.fshp.tech, with a certificate signed by a key only your hardware holds. Not even we can eavesdrop.
Download Flagship Studio on your computer
What's new in 0.3: local AI, a server you can check is yours, seven languages
How it works
Four steps. About ten minutes.
You bring the hardware and a mobile device. Everything else compresses into a USB stick, a QR scan, and a quiet daemon.
One USB, one reboot.
Flagship Studio writes your recipe to a stick. The disk encrypts on first boot. Your phone checks the server's own key with a six-digit code, then signs the unlock. Your subdomain comes up.
Vibe-code a service.
Describe what you want. An AI writes the code and its manifest, with your own key, Flagship Inference, or a model running on your own server. Your server builds it and runs it in its own sandbox.
Hand a friend a link.
Every service lives at app.you.fshp.tech. One tap to share, one tap to revoke.
Trust model
We structurally cannot read your content.
If we are compromised, what leaks is metadata (which servers exist and when they are online), never your files, messages or prompts. That isn't a promise, it's a property of the architecture.
fshp.tech handles identity: a username and a sealed blob it can't read. fshp.tech is a dumb pipe that routes raw TCP by SNI. TLS terminates on your hardware, with a Let's Encrypt certificate signed by a key only your daemon holds.
Mobile devices initiate every consequential action. Servers never call out unsolicited. No shared database in a third party decides who can see what. Every authorization is enforced by the data's own server.
The green padlock in your browser is real. It's signed by a key that lives on your hardware. Nobody else holds a copy.
Read the architecture
Questions
Honest questions, honest answers.
The questions that actually matter before you give us your trust. No marketing-speak, no clichés.
Why not just use iCloud, Google Drive, or Dropbox?
Because they read your data. We don't, and structurally we can't: TLS terminates on your hardware. That's the whole product.
What happens when I lose my mobile device?
If you set up cloud recovery (a passkey wraps your master key, ciphertext lives on .com), your new device unwraps it. If you didn't, the data's gone, like a hardware wallet that lost its seed phrase.
Do I need to be a developer?
No. The mobile app walks you through every step. Vibe-coding means typing what you want; the LLM writes it, the daemon ships it.
Can I use AI without sending my data to someone else's cloud?
Yes. Download a model to your server from its Local AI page. Your apps and builds can use it, and your prompts and data never leave your server. It runs on the processor, or on a graphics card once that card has been qualified.
Can I run this on a Raspberry Pi?
Not yet. The USB installer is for x86-64 PCs: NUCs, mini-PCs, old laptops. On arm64, Flagship Studio on an Apple-silicon Mac hosts your server in an arm64 virtual machine.
Is this open source?
Yes. BUSL-1.1, with automatic conversion to Apache 2.0 on May 3, 2030. Daemon, image-builder, mobile clients, webapp, protocol: all public.
What if Flagship the company goes away?
Your box keeps working. Your cert keeps renewing as long as Let's Encrypt is up. We can't lock you in because, structurally, we can't.
How does sharing work without a central account system?
Each pod issues signed invite tokens that are short-lived, revocable and scoped to one app. Authorization is enforced by the data's own server.
Take ten minutes.
Get the rest of your data back.
A USB stick, an old PC, a mobile device, and a vibe. We've kept it in production six months. Your turn.