Specifications
AI-MSL writes a plan for the work, and the plan is reviewed
Keep making the decisions you'd make with a development team. AI does the work around the clock, and senior engineers supervise the critical decisions.
Tell AI-MSL what you need, approve the requirements and price, and follow delivery in your MSL Portal. AI does the engineering. Experts check it at set review points called gates.
Start with a full picture of your software, an improvement plan, and an engineering advisor on call.
AI-MSL connects to your code repositories and runs a System Assessment. It then builds AppGraph, a living map of your software, its parts, its documentation, and your team's know-how.
Your AI Lifecycle Manager is like an experienced development manager or VP of Engineering you can call anytime.
Stop managing developers just to keep software updated, secure and ready to build on.
AI-MSL keeps checking for updates to the outside code your software relies on, security patches, maintenance needs, and upgrade opportunities.
Routine maintenance runs within your agreed scope. Anything larger comes to you for approval.
You or your product manager describe a feature. AI-MSL turns it into written requirements and an estimate you agree on.
Describe it in plain language, anytime. AI-MSL asks the right questions and prepares a Product Requirements Document (PRD), a written description of what to build.
Pay per Change, not for a retained team. Maintenance is a subscription; other development is estimated before you approve it.
Explore Pricing & DevCreditsFollow your Change through each stage while experts guide the AI and keep your software's design intact.
Once you approve, AI-MSL runs the engineering. You follow it in the Portal, with no developers or AI agents to coordinate.
AI-MSL writes a plan for the work, and the plan is reviewed
AI writes the code inside your existing software
Senior engineers check and correct key technical decisions at each gate
Tests run, the results get checked, and any problems found get fixed
You receive the finished Change with its tests and documentation
AI Lifecycle Engineers guide and check the AI's work instead of writing all the code. They keep each Change true to your software's design and easy to maintain.
Every Change arrives with the knowledge, evidence, and documentation to maintain it.
Before delivery, an engineer approves each Change based on its test results and evidence.
You, or your usual release process, add it to your main code and release it.
Your code and deliverables stay yours. Continue with your own team, another vendor, or AI tools anytime.
Add deployment, day-to-day operations, and monitoring, so issues in your live software feed straight into improvements.
CloudGeometry can manage releases, hosting, and monitoring on Kubernetes across AWS, Azure, GCP, and on-premises.
Problems, slowdowns, and ideas from your live software go back to AI-MSL as proposed Changes. They are prioritized and delivered with expert supervision.
Work with one provider from development to production.
Every supervised Change adds to your system's knowledge, so future AI work gets more precise.
AI-MSL keeps the approved decisions, knowledge, documentation, and test evidence from every Change.
Familiar tasks then need fewer questions, less correction, and less supervision. Engineers still sign off at every required gate.
With feedback from your live software, this leads to more proactive maintenance. Later, it leads to automating well-understood, low-risk Changes within agreed rules.
The Road to Self-HealingA managed service. AI-MSL is the full AI-powered software maintenance and development system, run on CloudGeometry's own platform and supervised by senior engineers at defined gates. You do not install, operate or prompt anything; you request, approve and receive.
No. Your AI Lifecycle Manager prepares each change cycle with you, explains estimates and answers product and technical questions. If you already have a product manager, they work directly in the Portal and the manager backs them up.
Yes. The Portal is open around the clock; describe what you want whenever it comes up. Requirements clarification starts immediately, and you decide when an approved Change goes into work.
A named CloudGeometry senior AI and application engineer who knows your system. They steer and correct the AI's decisions at each gate and sign off on every Change before it reaches you.
Read-only access to your repositories, plus whatever documentation, diagrams and operating notes you have. Nothing is migrated or rewritten; AI-MSL reads what you run today. Credentials are encrypted, access is scoped, and you can revoke it yourself at any time.
That is the normal case. AppGraph is built from the code first, then reconciled with your documents and with interviews of the people who know the system. The outdated documentation is replaced with generated documentation that is kept current after every Change.
You do. AppGraph, the documentation, the onboarding guide and every artifact produced for your system are yours, in your repositories and exportable. Your code is never used to train models.
Yes. Ask about priorities, trade-offs, what a feature would cost, whether a modernization is worth it, or how a competitor's capability could be built. Treat them as the VP of Engineering you can call without hiring one.
The Maintenance package covers proactive scanning of your dependencies, frameworks and security advisories, a prioritized maintenance queue, and the routine updates inside the agreed scope. Larger items are estimated as separate Changes. Scope and price are on the Plans & Pricing page.
None without your knowledge. Routine updates within the agreed maintenance scope run on the schedule you set and are reported in the Portal. Anything outside that scope, or anything that touches a component you have fenced, waits for your approval.
No. You approve the maintenance scope once, and routine fixes within it proceed. You approve individually only what falls outside it, which the Portal shows with impact and price.
Each one is estimated like any Change: impact, effort, risk if ignored and a fixed price, grounded in AppGraph. They sit on your list until you decide to schedule them. Nothing is charged until you approve.
No. Describe the outcome you want in everyday language. AI-MSL asks the questions a senior product manager would ask, checks the request against your system, and writes the PRD, including the edge cases and failure paths most requests forget.
Yes, as many times as you like before approval. Each revision re-checks the blast radius and updates the estimate. After approval, changes of scope are handled as a revision with a new estimate, never as surprise extra cost.
From your actual system. AppGraph tells us which components the Change touches, what depends on them and what has to be tested, and the estimate is built from that, not from a developer's guess. Estimates are stated in DevCredits; one DevCredit is one US dollar.
Nothing happens and nothing is charged. The PRD stays in your Portal; you can defer it, revise it or drop it. A Change rejected at a gate after approval is not charged either.
A named senior engineer who knows your system, at each gate. They do not write the code; they check that what the AI produced fits your architecture and product vision, correct its decisions where needed, and sign off before it moves on.
Yes. The Portal shows the Change at its current stage, who has signed which gate, what tests have run, and every artifact produced so far. Your AI Lifecycle Manager is available for anything the Portal does not answer.
It is caught at a gate or by the tests, corrected, and re-verified before you see the Change. The tests are generated from your requirements, not from the AI's code, and a separate verifier re-runs everything; a check that could not run is reported as not checked, never as passed.
Yes. Every Change follows your architecture and conventions, carries a specification and tests, and updates the documentation. Any developer, yours or another vendor's, can read and change it at any time. That is a condition of sign-off.
Tests on the code: build, unit tests, coverage against the changed area, static analysis, type checks, security, secrets, dependency and license scans. Tests in an integrated test environment: acceptance tests written from the PRD, integration, API, end-to-end and regression. The report names every test that ran and its result.
Yes. Every Change keeps who requested it, who approved it, what was tested and what was delivered, with chain of custody. That is the evidence a SOC 2, HIPAA or customer audit asks for, collected as a by-product of delivery. CloudGeometry itself is in the SOC 2 Type 1 audit now, with the report expected in December 2026; the Type 2 observation period follows.
You do, or your authorized release process. The Change arrives as a reviewed, tested branch and pull request in your repository. You merge to main and release on your schedule. If you prefer, CloudGeometry's optional release management service does it for you under the same supervision.
Yes, at any time. Your code, documentation, tests and audit records are in your repositories in standard form. You can carry on with your own employees, another vendor or AI tools. Nothing about the delivered software requires AI-MSL to keep working on it.
No. AI-MSL delivers to your repository and you run production wherever you do today. Hosting and production operations are optional services you can add if you want one provider from development to production.
Yes. CloudGeometry runs Kubernetes-based production on AWS, Azure, GCP and on-premises, in your account or ours. The same supervising engineers oversee releases and production as oversee your Changes.
With the Managed Production Operations service, CloudGeometry does: release readiness, deployment, monitoring, incident response and operational maintenance, with 24/7 support. Without it, you keep your current process and AI-MSL hands over at the pull request.
Yes, as proposals. Production findings, a failure, a performance regression, a recurring error, become proposed Changes in your Portal with impact and estimate. They go through the same approval and supervised lifecycle as any other Change; nothing is changed in your system because a monitor fired.
Yes, in a specific way. Every approved decision, correction, rule and test is kept in your system's knowledge, so the next Change is specified, estimated and built against a more complete picture of your product. Your knowledge stays yours and is never used for other clients' systems.
That is the direction, and you can see it. The Portal shows how many decisions needed a human on each Change and how that trend moves over time. More precise requirements, specifications, code and tests mean less of the engineer's time per Change.
Yes. Senior engineers sign the gates on every Change. Where supervision is reduced for well-understood, low-risk components, it is because you and the supervising engineer decided so for that component, never because the system decided on its own.
In steps, not on day one. Today: supervised AI delivery and automated maintenance. Next: production findings flowing in as proposed Changes, and reduced supervision on components you choose to fence. The Road to Self-Healing page shows what is live, what is in build, and the dates.
Start with an assessment of your software and your next Changes.