Skip to content

Digital sovereignty

Your fleet. Your rules. No walled garden.

Illustration: a glass cage with its front and top dissolved into light and its padlock open on the floor, the glass Confluence ring risen out of it and wired to three machines of its own.

Your machines, your models, your data. OmniConflux is designed to work with any vendor and never lock you in.

Nobody gets pigeonholed

A walled garden picks the vendor for you and keeps your work on its servers. OmniConflux is designed to do the opposite: to integrate with any vendor, run on what you own, and make leaving as easy as staying. OmniConflux is a desktop coding app for Omarchy, macOS on Apple silicon and Windows, version 0.3.0, in closed beta.

An agent locked in a glass cage with a padlock on its front wall

The walled garden

A locked vendor ecosystem, proprietary storage formats, and painful migrations if you ever want to leave.

The same cage unlocked: the padlock open, the walls dissolving into light, the agent free

Digital sovereignty

Open protocols, your own hardware, swappable models, and standard git repositories on your machines.

No landlord

In the design, your work is stored on machines you own, and your machines connect over SSH or an encrypted relay that carries traffic but is not where your work is stored. Vendor terms still apply to vendor tools and cloud models.

Any vendor

In the design, models come three ways: the vendor's own tool on your machine under your login, your own API key straight to the vendor, or local models on your hardware. The design lets you mix them in one fleet.

Swappable

In the design, you can change the model for one task or for all of them, and change the agent harness too. Any command-line agent is designed to run at the process level, and agents that speak MCP or ACP are designed to get deeper control.

Exportable

In the design, your work lands as commits in your own git repositories and as files on your own disks, so you can read it and take it with you.

Open standards

By design: OAuth 2.1 and OpenID Connect for sign-in, MCP for tools, A2A and ACP for agent coordination. Standards you can check, not a private handshake.

Your choice of help

Self-serve is the default design. If you want us to run a fleet for you, talk to us.

A managed fleet is planned, not live. It will run on your API keys or enterprise tokens, never on a personal subscription seat.

What sovereignty does not mean

It does not mean every vendor's terms disappear. When you use a vendor's subscription, the design runs that vendor's own tool on your machine under your login, as that vendor allows. By design, OmniConflux does not pool personal accounts, share one seat across many cloud agents, or pass your seat login through its servers. By design, agents share work through git and files, not through a claim of perfect memory across vendors.

Read the full details on the platform page and in the fleet architecture guide.

See it for yourself

Start with what connects, then read exactly what leaves your machine and when.

Questions

What does digital sovereignty mean for an agent platform?

In the design, you decide where the work runs, which vendors see it, and where the results live. OmniConflux is designed to run on your machines, work with any vendor you choose, and leave your work in your own git repositories.

Am I locked into one AI vendor?

No. By design, each task can use a different vendor or a local model, and a verifier from a different vendor checks the result. Switching vendors is designed to be a setting, not a migration.

What happens to my work if I stop using OmniConflux?

In the design, it stays where it already is, as commits in your repositories and files on your machines, and your keys and vendor logins stay with you too.

Do cloud models still see my prompts?

Yes, when you choose a cloud model, that vendor receives what you send it under its own terms. In the design, local models keep the work on your hardware, and the choice is yours per task.