bex is an open-source, self-hostable PaaS that positions itself as an AI-native alternative to Render, letting developers push Git and receive a deployed URL on their own Kubernetes infrastructure. Coding agents operate as first-class users via MCP alongside the dashboard, CLI, REST, and GraphQL interfaces, all backed by a shared Go core. The platform uses a Kubernetes operator with Cluster API for machine provisioning, supports Render-style `render.yaml` Blueprints for declarative service definitions, and ships managed Postgres, Key Value, logs, metrics, autoscaling, custom domains with TLS, and SSH access.
- 471 stars, 50 forks, 9 contributors — including Claude, Cursor, and Copilot listed as named GitHub contributors
- Apache-2.0 licensed; explicitly marked "not ready for production workloads" (public alpha)
- Language split: Go 58.5%, TypeScript 32.9%, Shell 6.7%
- Internal "lego" Go workspace enforces a strict `operator → types ← backend` one-way dependency DAG
- Tracks Render compatibility via an evidence-backed "parity ledger" (ADR018) rather than marketing claims
- Local quickstart provisions a kind cluster + Cluster API with Docker-container machines as tenant nodes
- Includes an Expo mobile app for safe supervision workflows (App Store listing present)
- Commit history references agent-driven QA rounds (w4/w5/w6 workstreams) and live dashboard re-probes
- 471 stars, 50 forks, 9 contributors — including Claude, Cursor, and Copilot listed as named GitHub contributors
- Apache-2.0 licensed; explicitly marked "not ready for production workloads" (public alpha)
- Language split: Go 58.5%, TypeScript 32.9%, Shell 6.7%
- Internal "lego" Go workspace enforces a strict `operator → types ← backend` one-way dependency DAG
- Tracks Render compatibility via an evidence-backed "parity ledger" (ADR018) rather than marketing claims
- Local quickstart provisions a kind cluster + Cluster API with Docker-container machines as tenant nodes
- Includes an Expo mobile app for safe supervision workflows (App Store listing present)
- Commit history references agent-driven QA rounds (w4/w5/w6 workstreams) and live dashboard re-probes
Leela Kumili writes about DoorDash's Flux platform, which moved LLM-based coding agent workloads from developer laptops to cloud infrastructure, automating 130,000 engineering tasks in a single month and supporting over 25,000 automated code reviews per week. The platform was built after local execution hit limits on power, uptime, and security, and is organized around four primitives: Firecracker microVM sandboxes, an in-house MCP gateway, YAML-defined playbooks, and multiple invocation surfaces (Slack, GitHub, cron, CLI, conversational interfaces).
- Sandboxes achieve a 95th percentile SLO under 5 seconds for full setup, including microVM start, repo clone, build tool install, and agent harness configuration.
- Playbooks can mix agent-driven steps with deterministic code where predictable execution or validation is required.
- The Agent Gateway enforces scoped permissions and logs all agent activity for auditing and policy enforcement.
- DoorDash switched Slack integration from private channels to public threads so engineers could observe agent executions and see how other teams delegated work.
- Sandboxes achieve a 95th percentile SLO under 5 seconds for full setup, including microVM start, repo clone, build tool install, and agent harness configuration.
- Playbooks can mix agent-driven steps with deterministic code where predictable execution or validation is required.
- The Agent Gateway enforces scoped permissions and logs all agent activity for auditing and policy enforcement.
- DoorDash switched Slack integration from private channels to public threads so engineers could observe agent executions and see how other teams delegated work.
As AI agents evolve from autocomplete tools to active contributors (opening PRs, managing infrastructure), DevOps must adapt. This playbook outlines the shift through these key strategic pillars:
* **Foundational Prerequisites:** Robust CI/CD, automated testing, and Infrastructure as Code are essential for agentic workflows.
* **Evolving Engineering Roles:** Engineers transition from code producers to system designers, agent operators, and quality stewards.
* **Structured Collaboration:** Integration across IDEs, PRs, pipelines, and production environments is required.
* **Repository Design:** Repositories must act as explicit interfaces using skill profiles and instruction files.
* **Development Methodology:** Shift from ephemeral prompt engineering to durable, specification-driven development.
* **Governance & Security:** Implement frameworks for custom agent consistency/auditability and transform CI/CD into active verifiers of semantic intent and security.
* **New Success Metrics:** Move from volume-based productivity counts to outcome-based and trust-boundary measurements.
* **Foundational Prerequisites:** Robust CI/CD, automated testing, and Infrastructure as Code are essential for agentic workflows.
* **Evolving Engineering Roles:** Engineers transition from code producers to system designers, agent operators, and quality stewards.
* **Structured Collaboration:** Integration across IDEs, PRs, pipelines, and production environments is required.
* **Repository Design:** Repositories must act as explicit interfaces using skill profiles and instruction files.
* **Development Methodology:** Shift from ephemeral prompt engineering to durable, specification-driven development.
* **Governance & Security:** Implement frameworks for custom agent consistency/auditability and transform CI/CD into active verifiers of semantic intent and security.
* **New Success Metrics:** Move from volume-based productivity counts to outcome-based and trust-boundary measurements.
Developers are replacing bloated MCP servers with Markdown skill files — cutting token costs by 100x. This article explores a two-layer architecture emerging in production AI systems, separating knowledge from execution. It details how skills (Markdown files) encode stable knowledge, while MCP servers handle runtime API interactions. The piece advocates for a layered approach to optimize context window usage, reduce costs, and improve agent reasoning by prioritizing knowledge representation in a version-controlled, accessible format.
