The waitlist is open

One human.
A whole company.

Run a company of agents from one map. Put them on pipelines, watch the work move stage to stage, and decide only where a human must.

One email when SoloINC is ready for you to install. Nothing else. Privacy.

Command Center
The SoloINC Command Center: eight cells, each with its pipelines drawn as rows of stage boxes, and the Desk panel with three decisions waiting
The Desk
The Desk: a decision open with Build, Abandon, Ask and Memo
  • Windows and macOS
  • Desk and Team apps on Android
  • Your machine, your models, your data
  • Nothing metered until you say so
  • Core is free

How a company runs

Every seat but yours is an agent.

01

A company is a map.

Cells for the businesses and departments. Under each, its pipelines: lines of stages a release, a ticket or a candidate moves along.

02

Agents work the stages.

Each stage is worked by an agent on your own machine, under the operating system's sandbox, delivering the document that stage produces.

03

You decide at the Desk.

What needs a person arrives as a memo, with the documents behind it. Nothing before the Desk asks you.

The console

The whole company, one screen deep.

Every box opens a panel. Nothing lives on a screen the map cannot reach.

The map

Every cell as a box, each cell's pipelines and workloads under it, the stages as a row you can press. The portfolio at a glance, and every count one click from its cause.

The map: cells with their pipelines as rows of stage boxes

The pipeline

A pipeline is one file: stages, the verbs between them, who answers for each, what each needs and produces. The map draws exactly what the file says. Items enter at the left and leave at the right.

A pipeline board: stage columns with cards planned, building and verifying

The Desk

What waits on a person, and only that. Approve, send back with a question, modify, or open the dossier. The Desk app on Android shows the same cards from anywhere.

The Desk with three decisions waiting

Ask

Ask the Managing Agent from any screen. “What is waiting on me today?” Nothing moves because of a sentence: a decision still goes through the Desk.

The Ask panel: a question to the Managing Agent and its answer

The record

Every console action on the audit log: who did it, what it changed and what it was before. Each cell's checkout and ledger is a git repository on your own disk.

The Activity record: decisions with their notes and who made them

The console's own screens, on a fictional company.

Pipelines as code

Declare it in one file. The map draws it.

Starter pipelines ship with Core. Onboarding offers five company templates, a software product company, a client services studio, a content and media business, a holding company and an online store, and hires an agent for every stage their pipelines call for.

Pro adds a catalog of more than three hundred ready-made steps. The release starter, counted →

release.pipeline.yaml · abridged
id: release
stages:
  - id: planned      # owner: human
  - id: building     # run: release-build   produces: notes.md
  - id: verifying    # run: release-verify  produces: verification.md
  - id: release-desk # gate: the Desk
transitions:
  - {from: planned,      to: building,     verb: build,   gate: human}
  - {from: building,     to: verifying,    verb: verify,  gate: agent}
  - {from: verifying,    to: release-desk, verb: submit,  gate: agent}
  - {from: release-desk, to: released,     verb: release, gate: human}

What it refuses to do

  • Spend money.
  • Sign anything.
  • Publish.
  • Contact a person.
  • Reach hosts you did not name.

Not “shouldn't.” Can't.

Those acts stay with the one human. Every workload runs under the operating system's sandbox, from a settings file it can read but not edit: no write outside its ledger, default-deny egress, no reach to the console or its state.

Bring the agents you already have. An imported agent starts untrusted: read-only tools, no MCP servers, no schedule, no memory, until you promote it. Kill switches stop an agent, a stage, a pipeline, a cell or everything.

The boundary is the operating system, not a prompt. Every concern, and what the product does about each →

Models

Your machine. Your models.

Nothing metered until you say so. Choose which channels work runs on, and in what order, in one company-wide setting.

The seat

Your Claude Code subscription.

The default. Metered by allowance, never by money.

Local engines

On your own hardware.

Ollama, MLX, llama.cpp, vLLM, LM Studio, run by SoloINC's native runtime. No Claude Code needed.

Metered providers

Off until you switch them on.

OpenAI, Gemini, OpenRouter, Anthropic's API, billed to your own account, only once the API switch is on.

Trust

Built against the concerns people actually have.

Nothing leaves your machine unless you open a door.Default-deny egress with the sources named. Licence keys are verified offline. Telemetry is a local file.
Agents propose. You decide.Every decision that needs a person arrives on the Desk as a memo with the documents behind it.
A kill switch that is not a prompt.Agent, stage, pipeline, cell or everything, read by every run before it starts.
Every action on the record.Who did it, what it changed and what it was before.
Budgets the agent cannot edit.A scheduled workload without a budget fails validation, and every run carries a turn cap.
Agents cannot change their rules.The contract and the guard machinery are protected paths a workload cannot write.

Core and Pro

Core is free. Pro is a key.

Core
Free

The console, the pipeline engine, the runtime, the starter pipelines and the demo company. Runs a company end to end.

  • One map of every cell and pipeline
  • The Desk and the memos
  • The sandbox, the kill switches, the record
  • The seat, local engines, the API switch
Pro
A key verified offline

A 14-day trial starts at first run. Checkout is by Paddle; refunds within 14 days.

  • More than three hundred ready-made steps
  • Department archetypes, roles and SSO
  • A Managing Agent that briefs you daily
  • The Desk and Team apps on Android

Core and Pro, in detail →

The short answers

FAQ

More in the documentation.

Does this spend money?

Not unless you tell it to. By default a workload runs on your Claude Code seat, metered by its allowance, never by money. A local engine costs nothing either. The API switch, metered providers and every funded account are yours to turn on.

Can an agent do something I did not allow?

Every workload runs under the operating system's sandbox with a settings file it cannot edit; the acts the contract reserves, spending, signing, publishing, contacting a real person, are not available to it. What reaches you arrives on the Desk.

Where is my data?

On your machine: the console's state, and each cell's checkout and ledger as git repositories you can read. The Desk app reads an encrypted copy of the Desk that the engine publishes to your own edge account.

Can I use it without Claude Code?

Yes. A workload runs on your Claude Code seat through the claude binary, or on SoloINC's own native runtime, which needs no Claude Code and runs on a provider key or a local engine. Both run in the same sandbox.

What do I need?

A Mac on macOS 14 or newer, or a PC on Windows 10 or 11, and something to think with: a Claude Code sign-in, a provider's API key, or a model on your own hardware. Nothing in the product asks you to open a terminal.

Linux?

No. SoloINC installs on macOS and Windows; the Desk and Team apps run on Android.

What happens when I join the waitlist?

We keep your address and write once, when SoloINC is ready for you to install. Nothing else, and you can ask us to delete it at support@soloinc.ai.

Who is behind it?

8086 LLC, a small New York software company.

Be one of the first
companies of one.

Leave an address. We write once, when SoloINC is ready for you to install.

We store your address and nothing else about you. Privacy.