➜ NextOS — an operating system in a browser tab.
An operating system.
In a browser tab.
A real desktop with a Unix-style filesystem and a terminal that runs an actual Python and an actual Node, not a subset of either - fifty-three built-in apps, and agents that ask before they change anything. Nothing to install: it runs in whatever browser is already open, on whatever screen you have.
the actual desktop - windows, the launch strip, and everything open in this tab right now
01Works where you work
Works where you work.
Laptop, phone, tablet, TV, the screen on your fridge.
Laptop
Windows, the strip, keyboard-first.
Phone
One app at a time. Add it to your home screen.
Tablet
The same desktop shell, run with a finger.
TV
Approve the day’s decisions from the couch.
Fridge / smart display
Check the schedule while cooking.
Nothing to install
It’s a web app. Add it to your home screen (or install it from a desktop browser’s address bar) and it opens full-screen, like an app — no store, no download.
Same OS, same files
Signed in, your files and tables follow you to the next device through the same sync as everything else in your account; turn on syncing for a given setting and it follows too.
Works offline
The OS itself keeps working with no connection — your files are already on the device you’re using. It syncs back up the moment you’re online again.
02What’s inside
The OS
A real desktop, files, terminal and fifty-plus apps, in any browser, on any device.
This is the operating-system part: a desktop with windows you drag and resize, a Unix-style filesystem that lives in your browser, and a terminal with a real Python and a real Node behind it - not a sandboxed subset, the actual interpreters. Fifty-three apps come with it, and third-party ones - including the apps the community builds - install from an App Store.
- Windows, a Unix-style filesystem, and a terminal that runs real Python and Node.
- Fifty-three built-in apps and an App Store for more.
- A built-in database every app, agent and website can use.
- Keep working without a connection; pick up on another device.
- Google Drive, OneDrive, Dropbox, Box, S3 and WebDAV sync.
03What’s inside
Agents and AI
Agents that work inside the OS with your files and apps, and ask before anything that matters.
Every app in NextOS is also something an agent can drive: open Finder, edit a file, send an email, follow a link. Anything that changes something - a write, a send, a payment - asks first, until you have told it that kind of action is fine to do on its own. Bring your own model key for any provider, or use the hosted model plane.
- Give an agent a task; it uses the apps, files and tools, under your approval.
- Ask in a sentence, or schedule it to run on its own.
- Bring your own keys for any provider, or use the hosted model plane.
- An OpenAI-compatible endpoint with caching, guardrails and routing.
- Multi-step pipelines that run in the background, on a schedule.
04What’s inside
Your business
A website the OS builds and hosts, and departments that keep it working.
The OS can run a business, too: describe what you sell in a sentence and it builds and hosts a real website on your own domain, with an editor you click straight into. Attach departments - marketing, sales, support, finance, legal - and they keep working after that, proposing what they'd do until you trust them to just do it.
- Tell it about your business; get a site, then a team that runs it.
- Built from a description, hosted on your domain, edited in place.
- Marketing, sales, support, finance and legal, working on approval.
- One daily briefing: calendar, inbox, approvals, what needs you.
- Products, checkout and subscriptions on your site.
05What’s inside
Teams and developers
Run it for a team with policy, budgets and audit, or build on it with the CLI, SDK and APIs.
Hand the whole thing to a team and it comes with what a team needs: shared workspaces, roles, SSO and SCIM, and a policy that is checked at the gateway, at run creation, and again by the runner - not just written down. Build on it yourself with the CLI, the SDK, or the OpenAI-compatible gateway.
- Shared workspaces, roles, SSO and SCIM.
- Policy, budgets, approvals and an audit trail for every agent.
- Keys stay in your browser unless you say otherwise. Encrypted at rest on the server.
- Scripts, deploys and runs from your terminal or your code.
- Test your agents like code, on every change.
06In three steps
How it works,
start to something that keeps running.
Every screenshot below is the actual product, not a mockup.
Sign in on any device
Google, GitHub, or an email and password. State lives in this browser by default; sign in and it syncs so the next device picks up exactly where this one left off.
sign in on any device
Your files, apps and agents are there
The same filesystem, the same open apps, the same agents and their history - not a fresh account on a new screen. Cross-tab and cross-device continuity, not a re-download.
your files, apps and agents are there
Agents and departments keep working while you’re away
A scheduled agent, a background run, or a department attached to a hosted site does not need this tab open. Approvals wait for you in one place, whichever device you open next.
agents and departments keep working while you’re away
07Pricing
Free to start.
One fee once you're running a business.
Hosting is $15/month on any plan, including Free. The full team of departments needs Plus, from $10/month. Every plan, compared
08Questions
Asked often,
answered plainly.
Is NextOS really an operating system?
Yes, in the sense that matters: a window manager, a Unix-style filesystem, a terminal with a real Python and a real Node behind it, and processes (agents, background runs) that keep going independent of any one window. It runs inside a browser tab instead of on bare metal, which is what lets it run on anything with a modern browser.
What runs on my device, and what runs on a server?
The desktop, the filesystem, the terminal runtimes and most apps run entirely in your browser - nothing to install, no server round-trip for everyday use. Anything that needs to keep running when the tab is closed (a scheduled agent, a background job, live sync, a hosted website) runs server-side, and only that part does.
Does it work on my phone, or a TV?
On anything with a modern browser: a phone or tablet gets a touch-first mobile shell instead of the desktop’s window manager, and a TV, a smart display, or a kiosk with a browser gets the same OS in whatever screen size that browser gives it. Install it as a PWA for an app-like icon and window.
Do my API keys and files leave the browser?
Your own model provider keys stay in your browser unless you explicitly turn on sync. Your files live in the browser’s storage by default; sign in and they sync to your own connected Google Drive (or six other storage providers) rather than to a server-side copy NextOS keeps.
What happens if I go offline?
The desktop, the filesystem, and anything already open keep working - the terminal, local apps, and files you already have. Anything that needs a model provider, sync, or a server-side feature waits for the connection to come back and picks up from there.
Can my whole team use it?
Yes - a Teams workspace adds shared roles, an admin-set policy on which providers, models and MCP servers a member may use, SSO by domain, and an audit trail, with that policy checked at the gateway, at run creation, and again by the runner before anything actually executes.
no install · runs in the browser you already have