Security
One component can write to your repository. You run it.
The sidecar runs on your machines, connects outward only, and keeps your repository credentials on your side.
01 · The perimeter
One write path, one thing to review.
Agent work comes back as branches and patches. Repository tokens are scoped to one repository, expire after an hour, and are never stored. The text of your repository is uploaded to Aktum for indexing and review.
Aktum · app.aktum.io
the studio · the backend · one Postgres
work as events, results as commands,
over authenticated HTTPS
Your infrastructure
The sidecarthe one you enrol and run
outbound only, no inbound port · your model keys
branches and patches for agent work
Your repository
repo credentials never leave your side
02 · Sidecars
You decide where jobs run.
Locally or in Docker, how many at once, and which hosts a job may reach. A Docker job's traffic goes through a proxy that allows only those hosts.
03 · The scribe
The AI drafts. A named person decides.
Three operations, and four actions it is never allowed. The run log lists them again after every run.
forbidden · 1Write a word of the specification.
forbidden · 2Approve, sign, or close a thread.
forbidden · 3Merge its own branch.
forbidden · 4Decide a gate rather than ask it.
04 · People
No passwords. A second factor on every session.
Sign in with GitHub, Google, an email link or a passkey. Signing always asks for a fresh second factor. Locking an account ends its sessions at once.
05 · Audit
Every change to people and settings has a name.
The audit log lists who changed people, roles and settings, and why. Filter it by person or action.
