The Future of AI-Native Software Delivery
Evolved from orchestration platform to building comprehensive organizational context
From infrastructure you operate, to infrastructure that works alongside you.
How Facets and Praxis evolve over the next two quarters, from October 2026 to March 2027.
Plans reflect current direction and may evolve.
An infrastructure-aware AI agent that works in chat, in AI coding assistants, and inside Git, CI and Slack.
Infrastructure import, now agent-led
With read-only cloud access, the agent reverse-engineers your infrastructure as code, provisions a managed environment and iterates until it matches production with zero drift.
Impact: Onboarding without re-platforming
Preview environments, now triggered from CI
A GitHub Actions step creates a per-branch ephemeral environment on any CI event.
Impact: Faster developer feedback loops
Custom skills, scaled into a marketplace
An internal marketplace with governance, where teams publish, version and roll out skills and workflows across the organization.
Impact: Reusable automation at scale
Agent usage & quality analytics
See adoption, task success rates and where the agent adds value, with feedback from every skill run going back into improving it.
Impact: Measurable return on AI
Agent memory, made long-term
The agent creates structured SQL stores for operational data and builds long-term memory of your environment.
Impact: Faster, more accurate answers
Knowledge graph, extended to the full stack
The knowledge graph grows from application repositories and cloud infrastructure to every layer of your estate, so the agent can explain any system, onboard engineers and debug across layers.
Impact: Faster debugging and knowledge transfer
Agent context, enriched with runbooks
Runbooks, documentation and post-mortems become part of the agent's context, so its recommendations follow your team's operating procedures.
Impact: Consistent, procedure-aligned responses
AI review of infrastructure PRs
The agent reviews IaC changes in the pull request and flags risk and blast radius before merge.
Impact: Change risk caught earlier
Auto-generated observability dashboards
The agent discovers your infrastructure components, pulls the relevant telemetry and builds a complete dashboard: health, per-service Kubernetes latency and alerts.
Impact: Full observability from day one
Shipped in the last quarter
June to September 2026
Agent CLI for AI coding assistants
Run infrastructure operations, debugging and queries from Claude Code, Cursor or Gemini CLI.
Infrastructure knowledge graph
A real-time map of services, dependencies and configuration, for blast-radius analysis before every change.
Scheduled & event-driven agents
Agents triggered on a cron schedule, by Slack events or by webhooks.
Autonomous incident response
Alerts trigger root-cause analysis and a proposed fix. A dedicated agent tunes noisy alert rules and checks them against the live cluster.
Integration ecosystem
Cloud, Kubernetes, GitHub, GitLab, Bitbucket, Slack and New Relic give agents both context and the ability to act.
Custom agents & skills
Teams package their own agents and playbooks and distribute them across the organization.
Product Comparison
Why Orchestration Beats Alternatives
| DIY platform | With Facets | |
|---|---|---|
| Time to production | 12–18 months to partial functionality | 4–8 weeks to production |
| Platform team cost | A dedicated team to build, then keep maintaining, project by project | 3X ops efficiency5 DevOps engineers → 2 platform engineers (GGX) |
| Effort per new environment | Weeks of manual work for every environment | 87.5% less effort64 → 8 person-weeks (Capillary) |
| DevOps toil | Manual glue scripts across 30+ tools | 80% less toilUp to 95% fewer ops tickets (Capillary) |
| Infrastructure cost | Environments duplicated per project; non-prod left running | 52% lower per-environment cost (Aster)70% lower non-prod cost (Purplle) · 12%–20% cloud savings (Vymo, MPL) |
| Delivery speed | Releases wait in a ticket queue | 8-25x faster shippingMPL 8X, Purplle 25x, GGX 25x |
| Proven at scale | Rebuilt for each workload | 350 apps, 1,500 engineers, 75% fewer DevOps ticketsFortune-50 automotive company |
Facets vs GitOps Solutions (ArgoCD, Flux)
Philosophy
Duct tape for existing systems
Coordination for new systems
Infrastructure
Assumes it already exists
Orchestrates provisioning first
Dependencies
No awareness between layers
Handles automatically across stack
Tool Coordination
Manual coordination required
Automated across all chains
Configuration
Manual setup of URLs, secrets
Auto-discovery via contracts
Deployment Scope
Kubernetes-only focus
Full-stack orchestration
Traditional Teams vs Facets-Powered Teams
Team Focus
Ticket processors
Innovation enablers
Environment Creation
Days to weeks waiting
Minutes self-service
Process
Separate infra/app workflows
Unified deployment pipeline
Standardization
Fragmented across teams
Enforced through contracts
Security
Audited after deployment
Built into contracts
Knowledge
Trapped in individuals
Codified in platform
Market Position
Gartner® Recognition
Featured in multiple Gartner® reports
- Hype Cycle™ for Platform Engineering, 2024 & 2025
- Hype Cycle™ for SRE 2024 & 2025
- Market Guide for Infrastructure Automation & Orchestration 2025
- Reference Architecture Brief: Infrastructure Platform Engineering, 2025
Industry Partnerships & Events
Strategic partnerships and recognition
- CNCF Silver Member
- Techcrunch Disrupt 2022
- Thought leadership in Infrastructure Platform Engineering Category
- AIxDevOps podcasts and office hours
Ready to Experience the Future?
See why leading companies choose orchestration over DIY platforms and context-driven AI in SDLC.