Solus is the workspace for running agents on your machines, in your cloud, and across your data.

A billing-service lead session in Solus coordinates seven agents (four done, two working, one waiting on a question about which customers move to metered prices first) while the dashboard worker's diff is open in a pane beside it.
Works with the tools your team already uses
  • Claude Code
  • Codex
  • GitHub
  • Jira
  • Linear
  • Confluence
  • Google Drive
  • Any MCP server
  1. 1

    Pick where it runs

    Your Mac, a server you own, or a host Solus runs for your organization.

    Run on
    Maya's MacBook Pro This Mac
    build-01 AWS, us-east-1
    agents-01 Run by Solus
  2. 2

    Give it your context

    Tickets, specs, errors, and data from any MCP server go straight into the prompt, through your own sign-in.

    Fix ACME-214 to match Rate limits spec then check 429 spike
  3. 3

    Follow it anywhere

    Start on your Mac, answer from your phone. It is one session, live on every device.

    Live on both
Solus Cloud

Every device, every host, one secure network.

Run Solus on your own computer with no account, on your own VMs and servers, or on hosts Solus runs for you. Sign in, and every device reaches every host.

  • On your computer, even offline

    Mac, Windows, or Linux, with no account. On your network, devices connect straight to the host, with or without Solus Cloud.

  • On your own VMs

    Install the server on any Linux or macOS machine, in any cloud or your own rack.

  • Hosted by Solus

    Managed hosts for your team, with every member kept apart.

Nothing to open

Your machines connect out. No ports to open, no VPN to run.

Your code stays home

Code and conversations live on your machines, never on ours.

Keys stay locked

Agents use your accounts without ever holding your keys.

You decide who's in

Remove a teammate, and their access ends within hours.

Connect your data

Every source your agents need, one sign-in each.

Solus is a full MCP client. Pick a server from the catalog or paste any address, sign in once, and every agent on every host can use it.

Solus MCP settings listing GitHub, Linear, Atlassian Rovo, Notion, Sentry, Slack and Context7 as installed and connected, above a catalog of more servers such as Figma, Vercel, Supabase and Neon, each with a Connect button.
Connect your tracker, docs, errors, and chat once, and every agent on the host can use them.
Jira ticket ACME-214 open as a Solus task: the spec, the Jira upstream link, the agent session working it, and a thread where the agent and two people answer each other.
Jira ACME-214 as a task, worked by an agent and two people.
Jira GitHub

Tickets become tasks

A Jira or GitHub issue opens as a Solus task with its spec and status. Start a session from it, and the task and the ticket stay in step.

A rollout runbook the agent wrote, open in Solus: a numbered table of contents, a decision summary, an open comment thread, and a Publish action in the header.
A runbook the agent wrote, ready to publish to Confluence.
Confluence Google Drive

Docs in, docs out

Agents read the real Confluence page or Google Doc. What they write publishes back, and edits made there pull back in.

The engineering loop

From ticket to pull request, and watched after it ships.

1 Delegate

Staff a task across agents.

A lead session splits the plan between Claude and Codex workers. Their questions and reports come back to the lead, and you can open any worker beside it.

The billing lead's question is answered with 'Free tier' and the worker reports are in; the Dashboard usage graph worker's transcript, open beside it, lists the six files it wrote in web-dashboard and its pull request #148.
2 Review

A second agent writes the review guide.

The guide walks the change in order, each part beside its code, and flags the tradeoffs to decide. Your line comments wait and go out as one review.

The Solus review guide for a rate-limiting pull request: the token-bucket section with a flagged tradeoff, its code beside it, and a pending line comment on the refill line.
3 Ship

Merge with checks and reviewers in view.

Or hand a conflicted branch back to an agent in its own worktree.

A pull request in Solus with its merge status, reviewers, passing checks, and every changed file with its line counts.
4 Monitor

Keep watch after it ships.

Automations triage new errors, check for drift, and keep dependencies current on a schedule. Each run is a session you can open and reply to, and a failure asks for your attention.

Solus Automations page listing eight automations across api-gateway, billing-service, web-dashboard, ios-app, infra and marketing-site, with recent run history, one needing attention and one paused.
Observability

See every turn, and what it cost.

Solus traces every turn on every host you use. See where the time went, what you spent, and what to fix, without wiring up a thing.

Every turn, from every host.

Spend, speed, and model for each turn, in one view. Ask a question in plain words or write SQL.

Insights in Solus: a chart of turns over the last 24 hours with spend, p50, and p95, and a table of every turn with its prompt, session, model, host, and duration.

One turn, step by step.

Open a turn to see where the time and money went, and what Solus thinks you should fix.

Solus Insights page for one turn, showing a span waterfall of thinking, file reads, edits, a failed test run behind a 26-second permission wait, a passing re-run and the response, with findings for the repeated test command and the time spent waiting on the user.

Frequently asked questions

Do I need Solus Cloud?

No. Solus runs on your own machine with no account. Signing in adds organizations, sharing, managed hosts, and sync.

Do I need an API key?

No. Solus drives the Claude Code and Codex tools you already have installed and signed in.

Where do my credentials live?

In one vault on the host, or in your Solus account. An agent never sees a token.

Where does my code go?

It stays on your machines and the hosts you add. Sharing a work or a task makes a cloud copy, only when you choose.

What does it run on?

Desktop apps for macOS 12 and later on Apple Silicon, Windows, and Linux; any browser; iPhone and Android; and a headless server for Linux or macOS.

What does it cost?

Free during the beta. The source is public under the Business Source License, which converts to Apache 2.0 in 2030.

Bring your agents. Bring your team.

Free and source-available. Install in a minute and use the subscription you already pay for.

Download for macOS
Also for WindowsLinux