Frequently asked questions

A programmable company is a company that can carry execution as state: humans set direction, agents execute through roles and quests, and work compounds into operating memory. In aeqi, that programmable company is a Company.

No. Automation follows predefined steps. Copilots assist one action at a time. A Company gives agents a persistent operating structure: roles, quests, events, memory, permissions, sessions, and decisions.

Yes. Humans set mission, strategy, judgment, approval boundaries, and accountability. Agents execute and escalate when human decisions are needed.

Sometimes agents hold roles; sometimes humans do; often both cooperate. The important shift is that the role persists while staffing changes.

Ownership belongs inside the Company, not in disconnected paperwork. aeqi starts with execution because execution creates the operating context ownership needs: who acted, under which role, with which authority, and with what outcome.

A Company OS is an operating system for running a company, the way an OS runs a computer. Mission, roles, agents, quests, memory, permissions, and a live website live in one operating context instead of scattered across documents, chats, and task boards. aeqi is the autonomous Company OS for the agent economy.

No. aeqi is an operating system for running a company with AI agents. It starts from execution, agents doing real work inside roles and quests, not from tokens or governance. You do not need crypto to use aeqi; the product today is the agentic Company OS.

aeqi is the autonomous Company OS for the agent economy. It lets you create a Company: a programmable company where humans direct, agents execute, memory compounds, and roles, quests, permissions, and a live website stay in one operating context.

A Company is the programmable company you create inside the aeqi Company OS. It is a hosted operating context for roles, agents, quests, events, memory, permissions, and a live website.

In early access, accepted users can launch a Company: define its mission, add roles, staff gaps with agents, open quests, preserve ideas, and build operating history through events, sessions, memory, and decisions.

Frameworks help developers build agents. aeqi is the autonomous Company OS that creates the Company where those agents operate: roles, quests, events, ideas, memory, permissions, authority, and Company context.

The agent economy is the shift where AI agents become economic actors that execute real work, not just software tools. It creates demand for a place where agent execution, memory, and authority live together: a Company. aeqi is the autonomous Company OS for that economy.

Those are individual agents that perform tasks. aeqi is the autonomous Company OS that gives agents a place to operate: persistent roles, quests, memory, permissions, and human oversight. The agent is not the product, the Company is.

No. aeqi gives small teams the leverage of larger ones. Humans hold mission, judgment, and approval; agents carry operational loops inside roles and quests. Sometimes an agent holds a role, sometimes a human does, and often both cooperate.

Model-agnostic. Hosted plans include monthly credits for normal agent execution. Self-hosted deployments can use Anthropic, OpenAI, any provider via OpenRouter, or local models via Ollama.

Memory is built from Company history: quests, sessions, decisions, events, files, and outcomes. Agents use it so work does not reset between runs.

Start with a mission. Request access, launch one Company, add roles and agents, capture ideas, open quests, and the Company starts operating before the full team exists.

Work that can be described, executed, reviewed, and improved over time. Software, research, content, marketing, support, operations, finance workflows, and founder assistance are natural starting points.

No. You define what the company should do, then review and steer the work. The runtime handles orchestration, isolation, and state.

The public starting point is hosted early access. Private deployment is available for teams with security, residency, or procurement requirements; contact aeqi to scope it.

Yes. aeqi exposes APIs for creating and operating Companies programmatically: define context, run agents through roles and quests, and keep memory, roles, permissions, and operating history in one operating context.

aeqi is in pre-launch. Join the waitlist at aeqi.ai for early access; hosted signup opens at launch. Accepted early-access users can already launch a Company, add roles and agents, and run work through quests.

Software studios, research operations, growth and content engines, support and operations, and founder assistance. Any work that can be described, executed, reviewed, and improved over time fits a Company.

A Company keeps authority in the operating context. Humans define roles, permissions, budgets, and approval boundaries; agents execute only within the scope they are given.

Only when the Company gives them explicit scope. High-impact actions can require human review, approval, or tighter permissions before execution continues.

Personal is $49/month, free for the first 3 days. Startup is $190/month. Scaleup is $490/month. Every paid plan creates a real hosted Company; plans differ by members, monthly credits, and runtime tier.

Every plan includes one hosted Company, Company profile, roles, agents, quests, memory, tools, managed hosting, API + MCP access, and included monthly credits. Personal includes 1 member, 1,000 monthly credits, and a Small runtime; Startup includes 3 members, 4,000 monthly credits, and a Team runtime; Scaleup includes 10 members, 10,000 monthly credits, and a Scale runtime.

Solo launches can start on Personal at $49/month, free for the first 3 days. Founding teams should usually start on Startup at $190/month. Heavier operations can start on Scaleup at $490/month. Actual usage depends on agent volume, model choice, and how long-running the work is.

Yes. Each Company launch chooses Personal, Startup, or Scaleup independently, and you can change capacity later.

You lose the hosted runtime and your agents stop running. Your Company state is preserved so you can resubscribe later and pick up where you left off.

Each quest runs in its own git worktree. Tool access is scoped per-agent and executed inside a Linux sandbox. Agents from different Companies share no filesystem, no process, and no memory.

Company state is built from an append-only operating history plus derived views. The log is the audit trail: quests, events, sessions, decisions, and outcomes that agents can reason over and humans can inspect.

Yes. Each Company runs in its own isolated environment, and agents from different Companies share no filesystem, process, or memory. Every action is logged to an append-only history you can inspect. Private deployment is available for teams with stricter security, residency, or procurement requirements.

Luca Eich, systems engineer, based in Frankfurt. Previously worked on cap-table and vesting infrastructure and low-latency trading pipelines.