Stop Writing Brittle `curl` Scripts in Your Pipeline.

You've written it. We've all written it. That fragile, unreadable chain of `curl` and `jq` commands in a bash script that calls an external API and prays the JSON schema never changes. It's a ticking time bomb. Custos replaces that technical debt with a single, declarative, and version-controlled JSON configuration file.

The Workflow:

Define a Gate

In your repository, you create a simple `.json` file that defines the gate's logic, including the API endpoint, evaluation criteria, and polling behavior.

Build Visually with the Configuration Studio

Launch a local UI to create your gate file. Instead of digging through API docs, you paste a sample JSON response, and the studio renders a clickable tree that automatically generates the correct query expressions.

Execute in Pipeline

In your CI/CD pipeline, you run the Custos container, telling it which configuration to use. Custos handles the polling, authentication, and evaluation, and returns the correct exit code to control the pipeline flow.

The Universal Switch for Your CI/CD Platform.

As an operator, your goal is to provide standard, reusable components, not to maintain a dozen bespoke scripts for a dozen different teams. Custos is a secure, stateless, and highly configurable container designed to be a universal building block for automating complex workflows and enforcing governance policies.

Platform_Context_Headline

• execute: The headless CI mode. Runs in your pipeline, loads a config file, and returns a pass/pause/fail exit code.
• interactive: The interactive local mode. Starts the Gate Configuration Studio UI for visually building and testing your gate logic.
• serve-docs: The offline documentation mode. Serves the tool's full documentation in an air-gapped environment.

Designed for Any Platform:

• CI-Agnostic: If it can run a container, it can run the Gate Controller. It uses standard environment variables and simple exit codes for communication.
• Configuration as Code: Gate logic is defined in `.gate.config.json` files, allowing teams to manage their own pipeline rules in a way that you can audit and govern centrally.
• Stateless & Ephemeral: The container holds no state. It runs, does its job based on its configuration, and disappears.

Licensing & Degraded Mode

Unambiguous Exit Codes

The tool communicates its decision clearly: `0` for Pass, `70` for Pause (a neutral state for timeouts), and `71` for Break (an explicit failure).

Never Break the Build

If a valid license cannot be acquired, Custos runs in a Degraded Mode. It logs a warning that the gate is not being enforced and immediately exits with code 0 (Pass), guaranteeing that a licensing issue will never block a critical deployment.