Positioning
Redgold covers three things that normally come from three separate products: infrastructure to deploy and run on, AI coding agents, and custom data pipelines. The recommended option is a Redgold-managed cluster, provisioned and operated by us. You can also deploy Redgold to your own cluster when you need to own the infrastructure. The comparisons below show which part of that surface each category covers and where Redgold extends beyond it.
The Redgold application shape comes from a small spec — a checked-in Rust serde schema encoded with CBOR, a pipeline manifest, an edge route, executor-run transform code, engine storage, and a GitOps deploy — running either on our managed cluster or on a cluster you deploy and operate yourself. In both models, an agent fleet operates the applications and platform. The comparison criteria are the deploy unit, execution model, data ownership, agent integration, and current product maturity.
vs managed app and cloud platforms
Heroku, Vercel, Railway, and Fly give you a clean path from a git push to a running app. They handle build, deploy, and scaling so you do not operate the infrastructure yourself. Raw AWS or GCP with Kubernetes gives you full control and every primitive you could want, at the cost of assembling and running it all.
Redgold puts managed deploys (ArgoCD and CI, container registries, multi-tenant and GPU provisioning) in the same place as the AI coding agents and the data layer. A PaaS primarily owns the path from application source to a hosted process. Redgold also owns the schemas, dataflows, datasets, model routing, and agent workspaces that produce and operate the application.
vs AI coding tools
Cursor, Devin, Claude Code, and self-hosted agent runners focus on the editing-and-iteration loop. They generally leave the infrastructure the agents run on and the data the agents draw from to the user — you bring your own cloud, deploy pipeline, and data plumbing around them.
Redgold runs AI coding agents (internal Claude-style agents and external AI agents) directly in isolated Kubernetes pods on the platform, with resumable sessions and queryable conversation, tool-call, and agent-state history. Model routing handles provider selection and rate limits. The Redgold scope begins where a model response or an editing session ends: persistent workspaces, fleet control, data access, review automation, and deployment live in the same system.
The all-in-one case
Redgold makes the three layers one platform. Whether you use the recommended Redgold-managed cluster or deploy to your own, the agents run on the same compute that deploys your apps, and both are fed by the same custom data pipelines. Piecing the equivalent together yourself means a PaaS, plus a separate AI coding tool, plus your own data and cloud infrastructure, plus the integration work to make them cooperate. Redgold's product boundary is the integrated system: agents, applications, data pipelines, and deployments share one schema and operational path.
| Capability | Redgold | Managed PaaS | AI coding tool | Raw AWS + k8s |
|---|---|---|---|---|
| App deploy automation | yes | yes | no | build it yourself |
| AI coding agents in managed pods | yes | no | editing loop only | build it yourself |
| Built-in model API and routing | yes | no | provider-specific | build it yourself |
| Custom data pipelines / data lake | yes | no | no | build it yourself |
Category comparisons
The sections above frame Redgold against whole-platform substitutes. The pages below give a criteria table for narrower product categories:
- vs a backend-as-a-service (Supabase, Firebase) — hosted CRUD, auth, storage, and client SDKs compared with pipeline applications.
- vs serverless compute (Modal and similar) — uploaded functions compared with dataflow execution over platform datasets.
- vs a do-it-yourself data stack (Kubernetes + Postgres + DuckDB + glue) — separately assembled components compared with one integrated application shape.
- vs Rama — a general JVM backend programming model compared with an agent-authored declarative platform.
- vs Apache Spark — a distributed analytics engine compared with a complete application runtime.
- vs Apache DataFusion — an embeddable query engine compared with an operated data and application platform.
- vs Heroku — a hosted application runtime compared with a Kubernetes, data, and agent platform.
- vs Lovable — an AI app builder compared with a data, deployment, and agent platform.
- vs AI model providers — model APIs compared with provider routing plus managed coding-agent operations.
- vs Cloudflare OS — an agent workspace with per-app isolate sandboxes compared with a data platform whose agents operate the cluster.