DEV Community

AndersonVitaease
AndersonVitaease

Posted on

I built an open MVP for deploying AI-built software without giving agents unrestricted server access

#ai #devops #deployment #opensource

AI can build software incredibly fast.

Putting that software into real infrastructure is a different problem.

An AI agent can write a working app in minutes, but there is still no good default answer for "how does this app actually get onto a server?" Either a human does everything by hand, or the agent gets unrestricted shell access to production. The first doesn't scale. The second is how small mistakes become big incidents.

Guardian Cloud is an open MVP for deploying small AI-built applications without giving an AI agent unrestricted authority over the server.

The positioning is one line: Deploy AI-built software with controlled execution.

The flow

The flow is intentionally simple:

  1. Paste a public GitHub repository.
  2. Guardian analyzes the application (Node.js apps are detected automatically; you provide the port when necessary).
  3. You see the deployment plan before any infrastructure changes.
  4. You explicitly approve the deployment.
  5. Guardian performs the controlled infrastructure actions, with bounded deployment monitoring, automatic domain provisioning and automatic HTTPS.
  6. The application is deployed, validated and exposed through its public application URL.

When success cannot be proven, the system says so: a failed build results in an honest FAILED state, never a fake success. Fail-closed is a feature.

What the current MVP supports

  • Public GitHub repositories
  • Node.js applications
  • Application detection
  • User-provided port when necessary
  • Deployment plan before execution
  • Explicit approval
  • Controlled deployment
  • Bounded deployment monitoring
  • Automatic domain provisioning
  • Automatic HTTPS
  • HTTP validation
  • Public application URL
  • Honest FAILED state when a build fails

Honest limitations

This is intentionally an early MVP:

  • Public repositories only, no private repos
  • Node.js only for now, no attempt to support every runtime yet
  • No dashboard, no billing, no teams, no custom domains
  • No claims of universal support, zero-risk execution or production-grade universal cloud

Kept-honest test evidence

Here is what the last validation round actually showed: an external Node.js sample repository was deployed and later served GET / = 200 publicly; another external Node.js repository (openshift/nodejs-ex) reached the deployment stage and failed honestly at the build step; the final end-to-end LIVE test used a small public Node.js test repository (AndersonVitaease/guardian-cloud-e2e) and reached a public HTTPS URL with GET / = 200. Claims don't go beyond that.

Try it

Guardian Cloud is open now:

https://guardian-cloud-mvp.2-25-96-245.nip.io

We are opening it now because we want real software and real users to expose the gaps instead of trying to predict every requirement in advance.

Give AI agents capabilities. Not unrestricted authority.

Top comments (0)