Skip to main content

Workflows that compose like Unix pipes.

Kubernetes-native. GitOps-driven. Build AI pipelines, automation, and real-time workflows — every component does one thing well.

GitOps-Native Control Plane

Deploy the Bobrapet operator and manage Stories, Engrams, and Impulses as Kubernetes CRDs. Everything lives in Git — use Flux, Argo CD, or plain kubectl.

  • Standard CRDs with admission webhooks for validation and mutation.
  • Reuse existing RBAC, quotas, and namespace policies — nothing proprietary.
  • Works with any GitOps controller that applies Kubernetes manifests.

Reusable Engram & Impulse Catalog

Engrams process data. Impulses trigger workflows from external events. Both are defined as templates with schema validation and shared through Git today. `bubu-registry` adds a Git-backed catalog and `bubu` CLI, while richer package guarantees remain on the roadmap.

Transport Optionality

Route data over Bobravoz gRPC with hub-and-spoke or peer-to-peer topologies. Transport selection is declarative per Story — swap transports without rewriting Engrams.

Why BubuStack

Kubernetes-native AI workflows. No proprietary runtime. No lock-in.

BubuStack is CRDs, controllers, and a Go SDK. Everything is declarative, everything lives in Git, and every component is replaceable.

Infrastructure as Code

Declare workflows, deploy with kubectl.

Stories, Engrams, and Impulses are Kubernetes CRDs. Apply them with your GitOps controller. The Bobrapet operator reconciles the rest — scheduling, retries, timeouts, and transport wiring.

  • Drift detection and rollout via standard Kubernetes reconciliation
  • Admission webhooks validate schemas before anything runs
  • ConfigMap-based operator tuning — no proprietary config layer
Launch the Quickstart
Reusable Modules

Build once, use everywhere.

EngramTemplates define inputs, outputs, and runtime requirements with JSON Schema. Version them, promote across environments, and distribute them through Git today. `bubu-registry` and the `bubu` CLI now cover registry-backed discovery and install flows; richer package guarantees are still roadmap work.

  • Supports Job, Deployment, and StatefulSet runtimes
  • Go SDK with testkit and conformance suites
  • Versioned promotion keeps staging and prod in sync
Create an Engram
State & Telemetry

Observe every run with traces, metrics, and structured errors.

StoryRuns and StepRuns emit OpenTelemetry traces and structured error reports. Payload offloading to S3-compatible storage keeps large outputs out of etcd.

  • OpenTelemetry trace propagation through the entire pipeline
  • Structured error contract with exit codes and retry classification
  • S3-compatible storage offloading for payloads and logs
View observability docs
How it works

From Git commit to running workflow.

BubuStack follows a simple path: declare resources in Git, let the operator reconcile, observe the results.

Developers

Build Engrams with the Go SDK. Test locally with the testkit. Push to Git and let the operator handle the rest.

  • Type-safe configuration and input binding
  • Local testing without a Kubernetes cluster
  • Structured errors with retry classification

Platform Engineers

Deploy the operator, tune the ConfigMap, set up observability. Standard Kubernetes operations.

  • ConfigMap-based tuning for scheduling, retries, and resources
  • OpenTelemetry integration for traces and metrics
  • Managed runner RBAC and guarded cross-namespace policies
01

Commit the Story

Write Story, Engram, and Impulse manifests alongside your application code. Push to Git.

  • Code review catches issues before anything runs.
  • Git history tracks every change to your workflows.
02

Reconcile with Bobrapet

Your GitOps controller applies the manifests. Bobrapet creates runtimes, wires transports, and schedules steps.

  • Bobravoz gRPC handles streaming transport with per-step tracing.
  • Admission webhooks validate resources before creation.
03

Measure StoryRuns

StoryRuns emit traces, structured errors, and payload references to your observability stack.

  • OpenTelemetry traces across the full workflow lifecycle.
  • Replay or debug failed runs from stored outputs.
BubuStack Ecosystem

Three components. One platform.

Each piece works independently. Together they form a complete AI workflow platform on Kubernetes.

Bobrapet Operator

Reconcile every Story like infrastructure.

Install once, register CRDs, and let your GitOps controller drive Stories, StepRuns, and Impulses with webhook-validated safety.

  • StoryRun, StepRun, Engram, Impulse, and Transport controllers.
  • Works with Argo CD, Flux, or any tool that applies Kubernetes manifests.
  • Admission webhooks validate schemas, immutability constraints, and references.
Operator quickstart
Engrams & Impulses

Package capabilities behind a stable interface.

Engrams process data. Impulses trigger workflows from external events. Both are defined as templates with schema validation and versioned promotion.

  • Go SDK for batch, streaming, and trigger (Impulse) workloads.
  • Supports Jobs, Deployments, and StatefulSets with autoscaling hints.
  • Browse existing components on GitHub — or build your own.
Building Engrams & Impulses
Stories & Transports

Compose DAGs and choose your data plane.

Stories wire Engrams into workflows with conditions, parallel execution, retries, and approval gates. Bobravoz gRPC provides the streaming transport.

  • Primitives: conditions, parallel, sleep, stop, executeStory, gate, wait.
  • Transport selection is declarative per Story — traceable in Git.
  • OpenTelemetry traces and Prometheus metrics across the pipeline.
Streaming contract
Community

Manifesto lives in Get Involved. This section mirrors the roadmap.

BubuStack is deployable today. The current limitations and direction are tracked in the roadmap, and contribution flow is documented in Get Involved.

What is missing today

  • No feedback loops / cycles — DAG-only by design.
  • No durable execution checkpoints or automatic replay on failure.
  • No mutable shared state between steps.
  • No mid-execution event injection into running workflows.
  • No mixed batch+streaming in one Story.

What is next

  • Manager RBAC redesign — preserve secret propagation and managed runner identity without broad cluster-wide mutation grants.
  • Artifact-backed runtime payload delivery — replace env-heavy runtime config with mounted runtime bundles.
  • Loop primitive — bounded iteration with exit conditions.
  • Workflow checkpointing — durable execution and restart recovery.
  • Registry hardening and catalog growth — SemVer-aware resolution, stronger validation, provenance, and more published templates.
  • Bubuilder authoring and deployment UX — replace the placeholder Story Builder and tighten shared-cluster auth guidance.
  • Python SDK with the same ABI contract as the Go SDK.
  • MCP gateway and native A2A protocol support.
  • Multi-cluster federation — global workflows across regions.
  • Compliance primitives — audit trails, cost attribution, EU AI Act traceability.

Where we need help

  • Test the platform on real workloads and open reproducible issues.
  • Improve docs and examples where onboarding is confusing, especially around registry and Bubuilder workflows.
  • Help redesign the manager security model without breaking secret propagation.
  • Expand the registry catalog and publishing UX for Engrams and Impulses.
  • Improve Bubuilder inspection, authoring, and shared-cluster UX.
  • Contribute testkit, transport adapters, and storage backends.

The canonical sources are Get Involved and Roadmap. Homepage summary stays in sync with those pages.

Declarative AI Workflows on Kubernetes

Define workflows as CRDs, deploy with your GitOps controller, observe with OpenTelemetry. Every change is versioned, reviewed, and deployed through standard Git workflows. Build new Engrams and Impulses, share them through Git today, and track registry expansion, Bubuilder authoring, operator hardening, and the remaining architectural gaps on the roadmap.