Self-hosted AI workspaces

For teams that want their own runtime

Give every AI goal its own workspace.

PromanOS keeps files, tools, models, and execution inside a dedicated Mini. A Mini is the isolated workspace runtime for one team goal.

Start with the Windows desktop app. Linux, Docker, and server bootstrap stay in Docs.

Trust

Concrete proof before you commit to a workflow.

PromanOS keeps the page calm, but the operating model is explicit: isolated Minis, self-hosted deployment paths, a flexible model stack, and a visible security posture.

Self-hosted

Deploy on desktop first, then move to your own host

Windows gets you started quickly. Linux and Docker use the same product model when you move to servers or team environments.

Mini

A Mini is one isolated workspace runtime

Keep prompts, files, tools, and runs inside a dedicated workspace for one goal instead of mixing them across teams.

Model stack

Use local models, hosted APIs, and your own tools

Swap providers without rebuilding the workspace surface every time the model layer changes.

Security

Restrictive CSP, security contact, and explicit routes

The public site ships with a restrictive CSP, publishes a security contact, and keeps deployment and data-path surfaces visible.

Why PromanOS

A calmer way to run AI work with your own stack.

PromanOS is designed to keep ownership, structure, and flexibility visible without turning the product into a control panel.

Self-hosted

Keep infrastructure on your side

Run on your own servers and keep control of runtime, secrets, and data paths.

Separate workspaces

Separate work by goal

Give product, ops, support, or research their own Mini so context stays clean and execution stays focused.

Switch models freely

Bring your model stack

Connect local models, hosted APIs, and your own tools without rewriting the workspace around them.

Use cases

Run launches, incidents, support, and research in separate Minis.

A Mini is a dedicated workspace runtime for one goal, so teams do not push every workflow through the same shared context window.

Product

Product team runs a launch Mini

Keep the brief, files, and execution path for one release in a workspace built around that launch.

Operations

Operations team handles incidents in a separate Mini

Isolate on-call context, runbooks, and recovery work so production incidents do not spill into other workflows.

Support

Support team triages requests without polluting product work

Keep customer context, repeated steps, and follow-up actions inside a dedicated support workspace.

Get started

Start on desktop. Move to servers when you need to.

Download for Windows first. Docs cover Linux and Docker once you need a longer-running host.

Full bootstrap steps stay in Docs.