A company of one.Run by youand your AI agents.
SingulaComp is the platform for the single-person company, operated by humans and AI agents. Your agents, their skills, your company memory and every connector live in one git repo you own — and the agents do the work on real cloud computers.
Free to start · No credit card required
A new kind of company. A git repository.
A company used to mean headcount, meetings and managers. A SingulaComp company is a repo you own: the agents, their skills, the memory, the connectors and the triggers are files in it — versioned, diffable, readable by a person and editable by an agent. You can grep your entire company.
You make the calls. Your agents do the work.
You, your agents and one repo. A whole company without headcount.
Invite members when you need them. Roles and per-resource permissions cover people and agents alike.
- SSales
- EEngineering
- MMarketing
- FFinance
- PPeople
- DData
Ask in the web app, or from Slack.
Start a session where you already are: in your project, or from a Slack thread. Each one boots its own cloud computer with the repo on it, does the work, and comes back with the result — a report, a deck, a change request, a reply.
Ask in chat and get it now.
The agent works and checks in for the calls that matter.
A cron schedule or a webhook starts the session while you sleep.
- Web app
- Slack
An agent for every job. Or write your own.
An agent is a markdown persona with a prompt and a tightly scoped reach into tools. Install one in a click from the marketplace, or write your own and commit it. Skills ride into every session, so what the company learns compounds.
Bring your own API key for any major provider, or sign in with the ChatGPT subscription you already pay for. The model is a line of configuration in your repo, so switching is a diff rather than a migration.
- SalesResearch, drafts and CRM hygiene, held for approval
- Builds the outbound campaign
- Stops before anything is sent
- EngineeringReproduce it, patch it, open the change request
- Reads the logs and ships the fix
- Opens a change request against main
- MarketingProduction work that sounds like you
- Runs the SEO programme weekly
- Rewrites land as change requests
- FinanceThe close, the reconciliation and the variance note
- Reconciles the ledger against the bank
- Chases the missing receipts
- PeopleScheduling, kits and onboarding — never the decision
- Sources and scores the pipeline
- Drafts the first approach
- ProductFeedback synthesised into specs, with the evidence
- Groups feedback into themes
- Takes the top one to a change request
- Data ScienceA real machine, a real query, an analysis you can re-run
- Queries the warehouse on a schedule
- Posts the chart to Slack
- Your own agentA markdown file in .singulacomp/opencode/agents/
- Define the role and its tools
- Give it the skills in the repo
Work lands as a change request you approve.
Every session runs on its own branch. When the agent wants to keep something, it commits and opens a change request toward main. You read the diff and decide whether it lands. Merge is default-deny for an agent unless you grant it in singulacomp.yaml.
- In reviewFix the forecast cache expiry+2 −1 · 118 tests passEEngineering
- Needs youSend the Harbor Point renewal proposalAsk set on send · 3 draftsSSales
- MergedWeekly API usage report for #metricsPosted to Slack · 06:00DData Science
Everything is code you own.
Every agent, skill, secret grant and trigger is a file you can read, diff and roll back. Run it on SingulaComp Cloud, in your own VPC or on your own on-prem network, with any model and your own keys. Clone the repo and the whole company comes with you.
From a blank project to a running company.
All of it in the web app. Nothing to install, no laptop involved.
- 01CreateCreate a project. It comes with a starter agent, its skills and its memory as files in a repo you own.
- 02ConnectPick a model with your own key, and connect the tools your company runs on — 3,000+ apps in a click.
- 03WorkStart a session. A cloud computer boots with your repo on it and the agent works on its own branch.
- 04LandThe agent opens a change request. You approve it, main keeps running, and triggers fire in the night.
Questions people ask before the first session.
Short answers, including the awkward ones.
- What does an agent actually run on?
- Its own machine. Every session boots an isolated Linux cloud computer with your repo and your tools already on it, on its own git branch — the session id, the sandbox id and the branch name are one and the same string. The agent can install, run and break anything inside it; only what it commits survives, because the machine is destroyed with everything on it.
- What stops it doing something I did not want?
- You set allow, ask or block per action, and a rule can match on a glob, a regular expression, or the arguments of the call itself. Be aware that nothing is switched on for you: a project with no policy declared runs every action, so this is a thing you configure rather than a thing you inherit. Session work reaches main through a change request, and merge is default-deny for an agent — an admin has to grant it in singulacomp.yaml, and that grant is itself an edit somebody else has to merge.
- Can I see everything an agent did?
- It is all recorded, on every plan. Recording is never gated — actions, approvals and the session transcript are captured whatever you pay. Reading, exporting and streaming that audit trail out to your own SIEM is an Enterprise entitlement, so on the lower plans the record exists but the export does not.
- Is my company data yours?
- No. A project is a git repository — clone it and the agents, the skills and everything the company has learned come with you. On an enterprise deployment the database, the files, the repos, the secrets and the audit record sit inside your own VPC or on-prem network. It is not air-gapped, and we will not pretend otherwise: agent sandboxes run on the compute provider you configure, and your instance has to be reachable so they can call back.
- Can I use the models I already pay for?
- Yes. Bring your own API key for any major provider, or sign in with the ChatGPT subscription you already pay for, or use the managed gateway and bring no key at all. The model is a line of configuration in your repo, so switching provider is a diff rather than a migration.
- What does it cost?
- Free is $0 — one project and 200 credits a month of sandbox compute, with your own key for any premium model. Team is $40 per seat per month and pools 2,500 credits a seat. Enterprise — including a deployment in your own VPC or on-prem — is custom pricing.
Run your whole company from one repo you own.
Start with one job and grow from there.
Free to start · No credit card required