ACE open-sourced ace-platform so teams can self-host its playbook-based context engineering workflow instead of relying only on the hosted service. Use it if you want MCP-compatible prompting infrastructure with your own Postgres, Redis, and deployment controls.

ACE's change is simple but useful for engineering teams: the platform behind its hosted product is now available as open source, and Daniel Mac says "you can now self-host" while the hosted service remains available the launch post. That turns ACE from a managed-only workflow into something teams can run inside their own environment.
The linked GitHub repo frames the project as a system for "agentic context engineering" rather than a generic chat wrapper. Its core unit is a playbook that "captures successful strategies, failures, and areas for improvement" so prompts evolve from real usage instead of staying static the repo summary.
The repo summary says ACE is designed to plug into MCP-supported workflows and specifically names Claude Code and Codex as compatible tools the repo summary. The practical angle is persistent context: teams can keep structured playbooks for coding, research, or analysis tasks, then reuse and refine them across runs instead of rebuilding prompt scaffolding each time.
For deployment, the same summary points to both Docker Compose and local development paths, with PostgreSQL, Redis, and FastAPI in the stack the repo summary. That gives teams an explicit self-hosting path, but it also means ACE lands closer to shared internal infrastructure than a lightweight local utility.
ACE is now open-source. Using ACE the past few weeks made me realize it should be available to everyone. It makes working with AI Coding Agents so much better. It's still available as a hosted service, and there are plans to improve ACE *A LOT*. But you can now self-host.
ACE GitHub Repo: github.com/DannyMac180/ac… Contributions and feedback are welcome.