Stop losing project context
Capture the why, plan, constraints, prompts, and lessons as a living project brain instead of scattering them across chats.
Project brain mission control
Amistio
Turn product intent into decisions, plans, prompts, and local-runner execution.
Plan work in the web app, keep the project brain in your repository, and run approved changes on your own machine. If the hosted product is not right yet, start with the open-source template and import later.
Brain folders
8Architecture, context, decisions, features, plans, prompts, memory, workflows
Execution
LocalApproved work runs through your paired runner, not a cloud code box
Fallback
TemplateStart open source today and import later if Amistio fits
Why it converts chaos into work
Give customers confidence before they ever sign in.
The homepage now answers the practical questions visitors bring with them: what Amistio does, where the work runs, how teams review it, and what happens if they want to stay open source first.
Review before execution
Turn wishes into reviewable ADRs, plans, specs, and implementation prompts before a runner touches the repository.
Keep the repo portable
Materialize approved brain documents into Markdown under `docs/` so your project memory stays versioned beside the code.
Keep source local
The web app coordinates work and status; your paired machine runs approved implementation with your local tools and credentials.
Workflow
From wish to reviewed work, without skipping the brain.
Amistio is not just a prompt box. It slows down the right parts of work so decisions, plans, and acceptance checks are visible before implementation starts.
1
Describe the wish
A founder, PM, or engineer writes the outcome they want in the web workspace.
2
Generate the brain
A local runner drafts or updates ADRs, plans, feature specs, memory, workflows, and prompts.
3
Review and approve
The team checks the proposed brain artifacts before implementation work becomes claimable.
4
Sync the repository
Approved Markdown files land in the repo control plane, ready for code review and local use.
5
Execute locally
The runner claims approved work, uses the chosen local AI tool, and reports progress back to Amistio.
Who gets value fastest
Built for people who need work to stay understandable.
The first product shape supports personal workspaces and team-oriented project coordination while keeping execution explicit and local.
Solo founders
Turn fast-moving product thoughts into durable decisions and runnable work without building a process stack first.
Product and engineering leads
Keep roadmap intent, architecture decisions, and implementation handoffs in one reviewable operating layer.
Agencies and studios
Give every client project a repeatable brain so context survives team swaps, pauses, and follow-up phases.
Platform teams
Coordinate multiple repositories while preserving local execution, approval gates, and searchable approved knowledge.
Trust boundary
A SaaS control plane, not cloud execution for your repository.
Amistio is designed for teams who want coordination, review, and status in a web product without handing arbitrary source execution to a remote worker.
No cloud source execution
Amistio coordinates the queue. Approved work runs from your paired checkout on your machine.
Markdown mirror
The project brain is not trapped in the SaaS. Approved files sync back into the repository.
Approval gate
Brain changes are reviewable before implementation work is released to a local runner.
Local first
Source, secrets, and toolchains stay on your machine.
The web app stores project state, reviewable brain records, queues, approvals, and runner status. The local CLI runner uses your repository checkout and your configured local AI tool to do the actual work.
Source filesNot uploaded for cloud execution
Runner credentialsStored on the local machine
Approved brainSynced as Markdown in the repo
What the workspace coordinates
A shared operating layer between product intent and local code changes.
Use the app to collect wishes, review generated project-brain artifacts, watch runner state, and keep accepted knowledge searchable and synced.
Project Brain
reviewWishShip onboarding without losing setup context
DecisionADR drafted for runner-first execution
PlanAcceptance checks and verification steps ready
RunnerWaiting for approval in paired checkout
Brain generationqueued locally
Approvalrequired before implementation
Executionpaired runner only
$ amistio sync pull
Materializing approved docs...
docs/plans and docs/decisions updated
MCP and tools
Make the tool layer understandable before customers ask.
Visitors comparing agent platforms need to know how tools, protocols, sessions, harnesses, and local execution fit together. Amistio explains the boundary clearly: the app coordinates, the project brain guides, and the paired runner uses local tools.
MCP vocabularyExplain Model Context Protocol without pretending Amistio currently ships a first-class MCP runtime.Local AI toolsShow how opencode, Claude, Codex, Copilot, Gemini, Aider, Cursor Agent, and custom commands fit.Tool sessionsKeep related work in context while starting fresh when old agent history would create drift.Harness safetyConnect tools to permissions, review gates, verification, and local runner execution.
Local runner flow
tool-aware Transparent by design
Do not want to use our product yet? Start with the open-source template.
Use the Amistio template to create the same project-brain folder structure in your repository without adopting the hosted app. If you change your mind in the future, you can import the repo into Amistio and continue from the brain you already built.
Docs are here
Read the guides behind the product.
The docs now have a visible home from the landing page: project brain files, template-first workflow, AI agents, MCP, tools, sessions, harnesses, and a practical AI history overview.
Product docsSetup, project-brain folders, CLI, pairing, sync, runner behavior, and troubleshooting.Project brainA visual map of memory, ADRs, plans, prompts, workflows, AGENTS.md, context, and architecture docs.Template guideUse the open-source template first and import later if the hosted workspace fits.What is an agent?A practical explanation of AI agents, tools, context, goals, and review gates.Agent harnessHow harnesses control permissions, verification, local runners, and safe execution.AI historyA concise timeline from symbolic AI to modern foundation-model agents.MCP guideWhat Model Context Protocol means for AI tools, context, and future-safe integration boundaries.Tools guideHow local AI tools, setup ownership, custom commands, and runner capability checks fit.Tool sessionsWhy Amistio reuses sessions only when related work makes that context useful.
Answers before signup
The practical questions are part of the page now.
Visitors should not have to guess whether Amistio is safe for private repositories, useful without a team, or compatible with a template-first workflow.
What if I do not want to use the hosted product?
Use the open-source Amistio template. It gives you the project-brain folders and starting structure without signing into the SaaS.
Can I import later if I change my mind?
Yes. Start with the template, keep the brain in your repo, and later use Amistio import from an existing checkout to bring accepted documents into the app.
Does Amistio upload or execute my source code in the cloud?
No. The product coordinates wishes, approvals, queues, and status. Repository work executes through the local CLI runner on your machine.
Is this only for engineering teams?
No. It is useful anywhere product intent has to become technical work: solo projects, client builds, product teams, and platform groups.
Choose your next step
Start hosted, start open source, or ask for a walkthrough.
Amistio should earn its place in the workflow. Open the app if you are ready, use the template if you want the brain first, or talk to us if you are deciding for a team.