FAQ
Questions we keep getting.
Direct answers. No placeholder prose.
Is AI running my business in production?
No. OneOps is a compiler, not a runtime. AI writes the code. Static, deterministic code runs the business. Every artifact (Terraform, GitHub Actions, runbooks, KPI queries) is committed to your repo and reviewed before it ships. AI workers are allowed inside the compiled structure in fixed roles the spec declares, plus agents for the outliers — never improvisation on the hot path. If we disappear tomorrow, the compiled code keeps running.
What about vendor lock-in?
Everything OneOps compiles lives in your GitHub org, in portable formats (Terraform, GitHub Actions, Bash/Python CLIs, Claude prompts). No proprietary runtime. Our work can be audited, forked, or maintained by any other engineer. That is the point.
Who owns the code after the engagement?
You. The customer owns every artifact. OneOps leaves no proprietary runtime dependency.
How is this different from a fractional CTO?
A fractional CTO gives advice. OneOps ships code, commits it, and hands over runbooks. The unit of delivery is a compiled platform, not hours or strategy memos.
How is this different from a DevOps consultancy?
Consultancies stop at cloud infrastructure. OneOps covers CRM, marketing, comms, tickets, payments, analytics, identity, and an AI agent layer as code too. The whole company, not just the servers.
Can you do this with our existing cloud?
Yes. Azure, GCP, AWS, and multi-cloud setups all work. The Terraform providers are pluggable. We adapt the catalog modules to whatever you already run.
What about SOC 2, HIPAA, GDPR?
OneOps ships standard artifacts: DPA template, incident response runbook, DR plan, vendor security scorecard, SOC 2 gap analysis template. Compliance lives in code alongside the rest.
What if we already have a platform team?
OneOps can augment as a Run-tier retainer, layering the catalog and agent fleet on top of what your team already ships. Or the platform team can use OneOps as a pattern library and run the compile themselves.
What can go wrong?
Honest answer: the only truly manual step is secrets onboarding (getting the keys for each vendor). Everything after that is compiled. If the vendor does not have an API, we do not pretend it does — we leave a runbook next to the code.
How fast can you move?
Assess (the Console Debt Report) is days. Foundation compile is weeks. Enterprise-grade SSO, SCIM, and SOC 2 rollouts are measured in months, not quarters.
Engage
Still have a question?
The fastest way to answer specific questions about your stack is a 30-minute call. No prep required.