Compute runtime
CPU and GPU application runtime with revisions, rollback, logs and secrets.
Pipelines
Builds and tests on isolated runners (Node, Python and Go) or on your self-hosted runner, with matrix, push, pull request and scheduled triggers, variables and secrets, JUnit reports, coverage and test policy. Time-boxed quarantine for flaky tests, test splitting by duration and selection by what changed; probable failure cause, AI explanation of the failed step, build summary, stage graph, per-step timing and failed and slowest tests on the run. Approvals that pause the run (policy or approval stage), with approvers, a deadline and decisions on screen, through the API and via webhook notices; a dependency cache on the managed runner per workspace, repository and lockfile, through signed URLs. Image builds from a Dockerfile (Kaniko, no Docker socket or privileged mode) pushed by digest to the workspace Artifact Registry, layer cache in the registry and image scanning as a gate. The managed runner serves public and private GitHub repositories, through the AIUBY GitHub App or a token.
Progressive Delivery
Canary and blue-green on Compute via Cloud Run traffic splitting: observed traffic steps, verification by revision health, error rate, latency and incidents, automatic traffic rollback on abort, policy approval before 100% and change windows.
Kubernetes & GitOps
Delivery to the customer Kubernetes cluster from a manifest folder (YAML + kustomization.yaml with images and replicas) in a connected repository: an agent installed in the cluster pulls the desired state over outbound HTTPS and applies only Deployments, Services and ConfigMaps in the environment namespace, with no cluster credential stored by AIUBY. A new commit on the environment branch becomes a diff and a rolling or replica-based canary rollout, with readiness reported by the agent, incidents, manual checks, policy, manifest rules and change windows, drift reporting, an application generator from a list of environments and production rollouts in DORA. Helm is not rendered (commit the helm template output); no traffic-based canary (service mesh/ingress).
Release Orchestration
A release as a set of applications promoted through ordered environments (dev, staging, production), gated before each one: freeze, change window, policy as code, passing E2E suite, scan with no open critical finding, per-resource queue, database migration applied at the commit and approval; a timeline with every gate, rollout and decision; Jira issue tracing; approve and roll back from the app, the API and the CLI (aiuby releases get, approve and rollback). Covers Kubernetes & GitOps applications; Compute is not part of releases.
Deployment Governance
Deployment freezes by period targeting Compute, Kubernetes and pipelines, which no approval overrides; policy before every Compute deployment with an approval request tied to the revision and config hash; requesters cannot approve and API keys never approve; minimum N approvals and approver groups; a Jira or ServiceNow change ticket as a condition; a screen with the workspace queue and freezes; events on webhooks, Slack included.
Delivery Controls
Checks between code and production: a dependency firewall enforced by CI and the npm proxy, artifact provenance, an IaC module registry and plans requested by the pipeline, test quarantine, splitting and selection, per-resource queues and database gates on releases, a per-environment application generator and Jira issue tracing, with every rule and block in the audit trail.
Repositories
GitHub repositories connected to the workspace with a read-only token (private ones included) and linked to the graph, CI and scanners; pipeline status checks published on the commit, which GitHub branch protection can require; full-text code search on the default branch from the app, the API and the aiuby-repo CLI. AIUBY does not host Git.
Infrastructure as Code
Managed plan and apply with OpenTofu in AIUBY's isolated executor: IaC workspaces (repository, directory, variables inherited from the environment, input sets and runner and approver roles), state always in your own S3 or GCS backend with locking, short-lived federated identity in your cloud (AWS and GCP), plans evaluated by IaC Review and the environment policy, apply only from a reviewed plan (by hash) with human approval, a per-workspace queue and scheduled read-only drift detection. Also: list-price cost estimates, blast radius with graph services, dependencies between workspaces, a versioned module registry, plans requested by the pipeline, plans commented on pull requests, time-boxed ephemeral workspaces and drift that becomes a Code Automation task. Does not store state or plans, does not create roles in your cloud, does not import resources and does not run Terraform (OpenTofu only).
Database DevOps
Database registry per environment (no connection address or credentials stored by AIUBY), history of the migrations CI or the runner applied and reported, a gate before applying (required rollback, passing migration check, promotion order and changed content), schema diff across environments from CI snapshots or the data connector with verified TLS, and database events in the audit trail. The customer's self-hosted runner applies Flyway or Liquibase SQL changelogs after another person approves the plan by hash, rolling the batch back if a migration fails; AI-written migrations go through the SQL rules and another person's review. The platform does not dry-run SQL.
IaC Review
Terraform/OpenTofu change review in CI: reads the PR .tf files or, preferably, the plan JSON produced in your CI with your credentials; flags destroys, replacements, hardcoded secrets, 0.0.0.0/0 and public buckets, estimates impact, detects drift against the last recorded apply and decides by environment policy (approval in the app). The platform does not run terraform and stores neither state nor the plan.
Database Migration Review
SQL migration review in CI (Postgres; basic MySQL), without connecting to your database: DROP, TRUNCATE, rewriting type changes, NOT NULL without DEFAULT, non-concurrent indexes, renames, expand and contract in one release and missing rollbacks, decided by environment policy. Does not apply migrations or diff schemas across environments.
Self-hosted Runner
Customer-owned runner (VM or Kubernetes), a pull agent with one key per runner, that runs CI jobs with up to 4 service containers, per-tool dependency and build caches, closed-catalog step plugins and CPU and memory metrics, plus Ansible playbooks and applying approved migrations, with the target credential kept only on its machine. Fork pull requests are blocked before dispatch.
Artifact Registry
Docker and npm repositories per workspace on AIUBY's Google Artifact Registry (São Paulo), with 15-minute push/pull credentials from a service account scoped to the organization, a catalog with digest, tags, size, date and publisher, links to repository and commit in the graph, provenance tied to the run, commit and digest, a dependency firewall with an npm proxy, audited retention policy, published and removed version events, per-repository access logs and a Compute deployment gate that rejects images without a scan or a verified signature when the workspace requires it. Cosign signatures verified against the workspace's ECDSA P-256 public key (no keyless or transparency log). Maven and PyPI are not supported.