AI-powered app builder
Describe the internal tool you need in plain words — a form, a tracker, a dashboard, a small workflow app. The AI agent writes the code, tests it in a sandbox iframe and shows you the live preview. As a no code app builder it asks nothing of you but the description; as an app creator no code teams can actually run, it puts the result straight into your workspace.
The apps you build run inside your uOS workspace and store their data through the platform, so there is nothing to deploy, no database to stand up and no hosting bill for the internal tools your team keeps asking for. Values your app stores for a user are encrypted client-side.
Edit the generated source on the Code tab if you want to. Upload assets. When a project is ready, install it in your workspace. App source and manifests are stored readable by the platform, because it has to run, review and AI-assist them — so keep secrets out of app code.
Studio has two different privacy boundaries — one for the apps you build, one for the data they store. Both are described below.
All authentication and key exchange uses NIST-standardized ML-DSA-65 (FIPS 204) signatures and ML-KEM-768 (FIPS 203) key encapsulation. There is zero RSA, zero elliptic-curve, zero classical-only crypto in the authentication path. Defeats store-now-decrypt-later attacks.
The name, manifest and full source of an app you build are stored unencrypted on the server. This is deliberate: the platform has to read them to render your app, power AI assistance and review submissions before publication. Do not put secrets in app source.
Values a Studio app saves for a user are encrypted in the browser before upload, so the server holds opaque ciphertext for them — though the keys they are filed under stay visible. An app needing fully private data semantics must encrypt inside the values it stores.
Your private keys are derived in your browser from three secrets only you control, and are held in memory for the session only — never written to browser storage, never sent to the server. A new device derives the same keys locally from the same three secrets.
UltimaOS runs in any modern browser — Chrome, Firefox, Safari, Edge. Nothing to install. Sign in by re-entering the three secrets your keys are derived from, and the same keys are rebuilt locally on whatever device you are using.
The name, manifest and source of an app you build are stored unencrypted, because the platform reads them to render your app, assist you with AI and review it before publication.
Values your app saves for a user are encrypted in the browser before upload, so the server holds ciphertext for them — though the keys they are filed under remain visible to the platform.
Any change you make is uploaded and picked up by every other device you are signed in on, so Studio looks the same wherever you open it.
Submit the app you built in Studio to the Marketplace. Reviewers check privacy and quality.
Upload assets to your project from Files. Assets inherit the same encryption as the rest of the workspace.
Studio projects can reference Documents for spec and design notes.
Studio publishes under your identity. Identity is bound to your private key, not a password.
UltimaOS runs in Chrome, Firefox, Safari and Edge. Nothing to install. Sign in with your passphrase to derive your private key locally.
The launcher shows every app. Studio is right there with its capsule video preview. Click to open.
Studio works alone, but it shines when combined with the rest of the UltimaOS apps. Same identity, same workspace, one place to work.
Short answer
Partly, and the split matters. The apps you build — their name, manifest and full source — are stored unencrypted, because the platform has to read them to render, review and AI-assist them. The data those apps store for a user is encrypted in your browser before upload, so the server holds ciphertext for the values (the keys they are filed under stay visible).
Short answer
Studio uses the same post-quantum stack as every other UltimaOS app: ML-DSA-65 (FIPS 204) for authentication, ML-KEM-768 (FIPS 203) for key encapsulation, XChaCha20-Poly1305 (RFC 8439) for symmetric encryption, and HKDF-SHA256 for key derivation.
Short answer
Yes. Sign in on any device by re-entering your three secrets and the same keys are derived locally, so your Studio content follows you. Changes sync live across all signed-in devices.
Short answer
Partly, and the split matters. The apps you build — their name, manifest and full source — are stored unencrypted, because the platform has to read them to render, review and AI-assist them. The data those apps store for a user is encrypted in your browser before upload, so the server holds ciphertext for the values (the keys they are filed under stay visible).
Short answer
UltimaOS is free for individuals and families — permanently, not as a trial. Organizations pay per seat once early access ends, and that is what funds the free accounts. There is no per-app add-on.
Short answer
Yes. UltimaOS supports encrypted export of all your content for backup and portability. The export is encrypted to a key you control; you can store it on your own infrastructure or in a personal encrypted backup.
Short answer
Yes. Apps built in Studio run inside the encrypted UltimaOS workspace — either locally for you, or published to the Marketplace for the broader community. Either way, the app runs inside the sandbox with the same cryptographic guarantees.
No ads, no data mining, no trial clock. Individual and family accounts are free — permanently. Organisations pay per seat, and that is what funds it.