Company profile · 4 min read
Amika: Software-factory infrastructure for coding agents
Amika provides shared cloud Rigs, sandboxes, workflows and controls for teams running coding agents across repositories and tools.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
Amika is infrastructure for building a software factory around coding agents. It fits teams that want reproducible sandboxes, shared agent sessions and control over the environment—not another chat window that writes code.
What it does
Amika’s docs call its cloud workstations “Rigs”: virtual machines loaded with a repository, development services, agent configuration and tools. Teams can start and steer agents from the web, Slack, Linear, an API, CLI, SSH, Codex or Cursor. A Rig can be short-lived for a PR or persistent for a shared environment.
The useful product boundary is the environment around the agent. Amika says a Rig can expose app previews, connect to GitHub, run agents from existing subscriptions and let teammates inspect or take over the same session. Its YC launch describes five primitives: sandboxed environments, workflows, deterministic guardrails, automated verification and audit trails.
Pricing and fit
Amika’s pricing page lists Free, Developer at $30/user/month and Team at $100/user/month. Each plan includes sandbox credits for compute, memory and storage; Enterprise is custom and adds BYO cloud or sandboxes, SSO, audit logs, compliance reports and SLA options. Amika says customers bring their own LLM keys and that it does not mark up token costs.
That is a clean distinction from a model subscription. The bill is platform access plus sandbox usage, while the team remains responsible for model keys. For a small developer experimenting with one agent, that may be extra infrastructure. For a team trying to reproduce environments, run background jobs or connect agents to CI, that is the point.
The founders are described in the YC profile as two-time YC founders building software-factory infrastructure. Dylan Mikus is described as a CMU computer-science and machine-learning graduate; both founders are named on the company’s public materials. Those are professional source facts, not proof that the product is easy to operate.
What could make it the wrong choice
Amika asks the team to take configuration seriously. The repository config, VM image, services, MCP servers, credentials and guardrails become part of the operating system. That is useful when reproducibility matters and overhead when the team only wants a quick code answer.
The practical test is whether the same Rig makes work safer and easier to review. If every task needs a bespoke environment, the factory metaphor may become another layer to maintain.
My editorial take
I would shortlist Amika for teams building recurring agent workflows around a real codebase: CI repair, scheduled maintenance, shared previews or multi-agent development. I would not start there for a solo founder who has not yet found a repeatable task. The product is strongest when environment drift—not model access—is the bottleneck.
Quick facts
| Field | Sourced detail |
|---|---|
| Product | Cloud workstations and sandboxes for agents and humans |
| Buyers | Engineering teams building repeatable software-factory workflows |
| Pricing | Free; Developer $30/user/month; Team $100/user/month; Enterprise custom |
| Usage model | Bring your own model keys; sandbox credits cover resource usage |
| Enterprise controls | BYO cloud, SSO, audit logs, compliance reports and custom infrastructure |
Sources checked
| Source | Checked |
|---|---|
| YC profile | 2026-09-19 |
| Amika homepage | 2026-09-19 |
| Pricing | 2026-09-19 |
| Docs | 2026-09-19 |
Cohort context
Amika is listed in Fall 2025. In our 2026-09-18 directory snapshot, 90 of 146 listed companies in that cohort have YC’s primary industry label B2B (61.6%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19T16:14:53.121Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Not observed in this response |
| H1 or H2 heading | Observed |
| Typed structured data | Not observed in this response |
| Docs/developer link | Observed |
| Pricing link | Observed |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
About the author
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.
First1000 ↗ · X ↗