Skip to main content

A control plane for CI and infrastructure:
the process and the resource in one model.

Graphene is for automation that must manage both work and the infrastructure where it runs. A pipeline is a typed Go program. Machines, containers, Kubernetes objects, files, and artifacts are durable resources with state, an owner, and a lifetime.

That shared model solves the gap between CI, which normally sees only steps, and IaC, which normally sees only desired state.

What changes in practice​

NeedGraphene model
Create an environment for one test runThe run owns the resource tree; terminal completion finalizes it
Keep a failed environment for investigationTransfer its subtree to the pipeline stand, optionally with a TTL
Work on a remote or existing machineIts agent connects outward; actions need no inbound control port
Reuse data between pipelinesPublish and attach a durable artifact record
Recover from a worker crashExecution resumes against recorded resources instead of recreating them blindly
Explain a failureRead the same record's state, events, logs, metrics, and traces

Resource libraries bring typed implementations without changing this model. The current libraries cover Docker, Kubernetes and Crossplane, Git, and files.

Choose a path​

If you want to…Start here
Understand the product and its current boundaryCurrent state → What you can build
Try it without running a serverFirst local plan
Run a complete local workflowFirst development run
Write a pipelinePipeline binary commands → Main → Core SDK reference
Operate from the command linegraphenectl
Operate visuallyGraphene Studio
Integrate another clientManagement API
Configure or diagnose an installationOperations

Current boundary​

The repository provides a complete development installation, not a hardened production distribution. Go is the only built-in pipeline authoring API. Pkl/KCL and a language-neutral YAML pipeline format are not current product surfaces. Exact shipped and unfinished capabilities are kept in Current state.