FAQ
Questions, answered.
What people ask before they try Aktum, what you need to run it, and what comes next.
"Another AI notetaker."
The output is a change to your repository, not a summary. Notetakers make documents about meetings. Aktum's work comes back as branches and patches against your repository, and a named person answered and signed along the way.
"Our specs are fine."
Your spec already answers questions nobody remembers deciding. A requirement says 10 requests per second, and nobody can say who chose that number. Somewhere between the meeting and the spec, whoever was typing decided it. Aktum sends that question to the person who can answer it, and records who did.
"We don't want AI writing our specs."
Neither does Aktum. The AI works under four forbidden actions, shown before and after every run. It only writes drafts, and only a named person can accept a draft into the spec.
"Where does our code go."
Only the sidecar on your own machines can write to your repository. Agent work comes back as branches and patches, and a settings change as a pull request or a commit you can see. Your repository credentials never leave your side. The text of your repository is uploaded to Aktum for indexing and review. On GitHub, Aktum reads your repository through a GitHub App you install and can revoke.
"What if Aktum dies."
The record survives. Everything Aktum records is committed to your repository as plain YAML files. You can read them in any text editor, in ten years, without the tool.
What you need, and what you do not.
What you need
- A repository. On GitHub, or on your own machines. Aktum works on the repository you already have; there is nothing to migrate.
- Somewhere to run the sidecar. One component, from Docker or a checkout, on infrastructure you control. It connects outward only and opens no inbound port.
- A model key of your own. Anthropic or OpenRouter for the coding agent; any OpenAI-compatible endpoint for quick help in the editor. The key stays on your sidecar or is stored encrypted in Aktum.
- Someone who can merge. On GitHub, setup is a pull request titled "Set up Aktum on this repository", and it waits until a human with write access merges it.
- A second factor. An authenticator app or a passkey, for every session. Your organization's policy can require it for every member, and cannot turn it off for anyone.
What you do not need
- To hand over repository credentials. Repo credentials never leave your side. Repository write access exists only through the sidecar.
-
To move your specs anywhere. The record is committed to your
repository as readable text, under
.aktum/, and it is readable in a text editor without the tool. - To change how your team ships. Work comes back as branches and patches you review in your own process. Aktum merges no agent work.
- To install anything for the team. The studio is a browser tab. Only the sidecar runs on a machine.
- A card. Early access is free while the beta runs, and no plan starts by itself.
Where this goes
These are plans, not promises. No dates.
- Planned: upload a recording of a meeting you already had, and get a change proposal back.
- Planned: questionnaires without an account. A signed link that expires, a few short questions, and the answers become part of the record.
- Planned: workshop mode. A live session where a domain expert joins by signed link, and the session ends as a change proposal.
- Planned: an MCP interface, so a coding agent can send work through the same review process.
- Planned: a local mode. The workspace, the checks, and the record on one repository, with no cloud and no account.
- Planned: pull request checks that block a change until the spec's required reviewers have signed the current version.