Free for you. Early access for everything else.

We run a small Ikenga server for you, in the region you pick. It is yours alone: one server per person, never shared with strangers. Pick a size, and change it later.

Or deploy the same server into your own cloud account in one click. You pay your cloud provider for the server, and nothing to us for it.

Every Personal plan includes an allowance of decision tokens for the Ikenga decisions model, which is in development. Use beyond the allowance is metered. Your engines keep using your own Claude Code, Codex or OpenRouter sign-in or key; we do not resell model use.

• Lite 2 GB RAM Sleeps when idle and wakes on your next request. Long agent runs pause while it sleeps.

  EU (Germany or Finland)

  $12

  US

  $12

• Small 2 vCPU · 4 GB RAM · 40 GB disk

  EU (Germany or Finland)

  $14

  US

  $28–32

• Medium 4 vCPU · 8 GB RAM · 80 GB disk

  EU (Germany or Finland)

  $18

  US

  $49

• Large 8 vCPU · 16 GB RAM · 160 GB disk

  EU (Germany or Finland)

  $28

  US

  $91

Asia and Africa: priced on request. Every price is per month, before VAT, and indicative until launch.

Personal goes on sale once we can set up each server without a person in the loop. Until then it is a waitlist.

$20 per member per month, billed annually, or $25 billed monthly. Early-access price.

We count members, not seats. A member is a person with the Owner or Operator role. Reviewers and time-limited Guests are free. If you use the desktop app without a server, a member is a named person covered by your support agreement. A seat is something else: a named slot for an agent session in a project. Seats are always free and unlimited.

Team is set up with you, not through a checkout. You get priority support in business hours, and help putting Ikenga in front of your team.

What a team gets from Ikenga today

$40 per member per month, billed annually, with a minimum of 5 members. Early-access price. Members are counted the same way as on Team.

Enterprise adds support with an SLA, help running your own multi-user server, and custom builds. Add a managed instance if you would rather we run the server for you.

How Ikenga handles security

An add-on to Enterprise: a dedicated multi-user server for your organisation, operated by us. It is priced per organisation per month by size, on top of your Enterprise members. Members on one server are trusted with each other; it is not built to keep untrusted customers apart.

• Small $150 per organisation per month 8 GB RAM · 2 vCPU · 80 GB disk For up to 10 membersestimate
• Standard $250 per organisation per month 16 GB RAM · 4 or more vCPU · 160 GB disk For up to 25 membersestimate
• Large $450 per organisation per month 32 GB RAM · 8 vCPU · 240 GB disk For up to 50 membersestimate

• EU (Germany or Finland) list price
• US (Virginia or Oregon) list price
• Africa (Johannesburg, Cape Town, Lagos) by quote

Member counts are estimates until we have measured each size under real use. Early-access prices.

Paid plans never take a feature away from Free. This is what every plan, Free included, gets today. Each feature shows its status and its limits.

In the desktop app

• Project, companion and store workspace Since 0.11.0
• Agent companion Since 0.11.0
• Choice of coding engine Since 0.7.0
  • OpenRouter sessions cannot resume after a restart.
• Agent seats Beta Since 0.16.1
  • New in 0.16.1 and still settling.
  • Figures an engine does not report, such as cost, show as a dash.
  • On an engine that cannot resume after a restart (OpenRouter), a vacant seat is marked not resumable and never silently starts a new session.
• Permission inbox Since 0.8.3
  • Only terminals that Ikenga starts are tracked; a claude started by hand in another shell is not.
  • Holding a tool call until you decide is opt-in for each terminal and off by default.
• Live cost meter Since 0.8.3
  • Only terminals that Ikenga starts are tracked; a claude started by hand in another shell is not.
• Live tool-call feed Since 0.8.3
  • Only terminals that Ikenga starts are tracked; a claude started by hand in another shell is not.
• Git change ledger Since 0.8.3
  • Only terminals that Ikenga starts are tracked; a claude started by hand in another shell is not.
• App and extension store Since 0.17.0
• Permission consent at install Since 0.17.0
• Install from a Git URL or npx Beta Since 0.18.0
  • Public Git sources only; credential prompts are disabled.
  • Sources outside the signed catalog are unsigned, and you must acknowledge that before installing.
• Signed registry of apps and extensions Since 0.1.0
  • The index lists only packages Ikenga publishes itself today.
• Passphrase vault Since 0.13.0
  • On Linux the vault uses Secret Service, with a read-only keyutils fallback.
• App lock Beta Since 0.16.1
  • Work already running keeps running while the app is locked; the lock screen lists it.
• Artifact grid Since 0.0.5
• Held updates that ask for new permissions Since 0.14.0
• Trust-gated capabilities for apps and extensions Since 0.2.9
• Personal and project scope for apps Since 0.17.0
• Settings with personal and project scope Since 0.13.0
• Backup restore wizard Beta Since 0.14.0
• Claude Code engine Since 0.7.0
  • Uses your own Claude Code installation and sign-in.

On a server you run

The desktop download does not include a server. These features need one that you build and run yourself.

• Headless server for one user Beta Since 0.8.1
  • Not part of the desktop download: you build and deploy the server yourself.
  • Access is by the server's shared token, or by pairing a device (pairing is new in 0.19.0).
  • The Devices screen shows how the server is exposed to the network, read-only; it does not change it.
• Multi-user server Beta Since 0.19.0
  • Members of one organisation share the server and are mutually trusted; it is not built for untrusted tenants.
  • Sign-in is by username and password; single sign-on is not available yet.
  • The server needs a Linux host: it runs as root under systemd and gives each person their own Unix user.
  • Not part of the desktop download: you build and deploy the server yourself.
• Members, roles and invites Beta Since 0.19.0
  • The spend cap is shown but not enforced.
  • Invites are links you copy and send yourself; Ikenga does not send email.
  • Ownership cannot be transferred yet.
  • Work done through a share never uses the owner's secrets.
• Device pairing and phone-sized remote client Beta Since 0.19.0
  • Pairing is covered by automated tests; a check with a real phone over Tailscale is still to come.
  • Behind a reverse proxy such as Caddy or tailscale serve, pairing a phone can fail with a "cookie_rejected" message, because the server sees the proxy's address.
• Approval routing across devices and people Beta Since 0.19.0
  • Today a paired device can answer permission requests raised by the desktop app. On a multi-user server the routing rules are built and tested, but the server's agent engines do not raise permission requests yet.
• Hash-chained audit log Beta Since 0.19.0
  • Export to external logging tools is not available.
  • Removing only the newest entries from the log may not be detected.
• Per-member secrets on a server Beta Since 0.19.0
  • Secrets are sealed under a key the server operator holds; a lost key cannot be recreated, so back it up.
  • A secret value can be at most 64 KiB, and one person's store at most 8 MiB; a write past either is refused.
  • There is no command to rotate the server's key yet.

These are on the roadmap. None of them has shipped.

• Signed installers for macOS and Windows Next
  • Current downloads are not code-signed or notarized, so macOS and Windows show a warning the first time you open Ikenga.
• Sign in with your identity provider Next
  • Until it arrives, a multi-user server signs people in with a username and password.
  • Covers OpenID Connect (OIDC) only. Most directories, including Active Directory through Microsoft Entra ID, connect through OIDC.
• Apps in the browser Next
  • Not available yet: installed apps run in the desktop app only.

See the roadmap

We are working with a small group of design partners and a waitlist. For Team and Enterprise, we won't take payment or sign a paid contract until our installers are code-signed. Personal ships no installer, so it does not wait for signing; it opens once its servers can be set up automatically.

Prices on this page are early-access prices, and Personal prices are indicative until launch.