Private beta deployment

Deploy one core.
Configure every instance.

Neutron is a self-hosted application, not a hosted control plane. The same image serves the API and web product; an instance file supplies product defaults, Postgres stores application state, and your chosen secret backend holds operational credentials.

Request access →Inspect configuration
01

Deployment contract

Start with the core runtime. Add the workflow sidecar when the instance needs encrypted vault operations or durable schedules.

Neutron image

Bun and Hono serve the API; the built web application is delivered from the same container and port.

Postgres

Threads, messages, runs, approvals, cards, users, settings, resources, capabilities, and usage persist in Postgres.

Instance configuration

instance.yaml sets identity, administrators, defaults, connectors, channels, workspace behavior, and safety posture.

Provider and service credentials

Connect provider subscriptions or keys through the provider control plane; keep Git host and integration credentials in the configured secret backend.

Assay-engine sidecar

The bundled sidecar supplies encrypted vault storage, cron, and durable workflows for schedules. The Helm component can provision it with persistent storage.

02

Current instance schema

This excerpt enables an approval-gated workspace and the connectors used for schedules and the encrypted vault.

# instance.yaml
name: acme
admins: ["[email protected]"]
theme: { brand: "Acme Core" }

safety: { mode: approval-gated }
connectors: [vault, schedule]

workspace:
  enabled: true
  autonomy: gated
  repos:
    - url: https://github.com/acme/platform
      host: github
      default_branch: main

channels:
  github:
    enabled: true
    bot_username: acme-neutron
    projects: ["acme/platform"]
SAFETY MODE

Use the current enum

readonly, approval-gated, and readwrite are the valid values. Tool policy can narrow the default.

WORKSPACE

Writable work needs a writable posture

An enabled workspace must use approval-gated or readwrite. Interactive turns can pause gated work; headless and channel turns deny it without a live approval bridge.

03

Container runtime

The minimal core needs a database URL and mounted instance file. Provider authentication is supplied through the selected adapter and secret backend.

docker run --rm -p 8080:8080   -e DATABASE_URL=postgres://neutron:password@postgres/neutron   -e NEUTRON_INSTANCE=/config/instance.yaml   -v ./instance.yaml:/config/instance.yaml:ro   registry.gitlab.com/bizfoundry/core/neutron:<version>

This command starts the core only. The configured vault and schedule connectors remain unavailable until a separate assay-engine process is reachable through ASSAY_ENGINE_URL and ASSAY_ADMIN_KEY; inject both from your deployment secret store. The private-beta image requires registry access.

04

Kubernetes component

The Helm component renders one Deployment and instance ConfigMap per entry. Enabling assay-engine adds its sidecar, workflow configuration, and persistent volume.

instances:
  acme:
    host: agent.acme.example
    assayEngine:
      enabled: true
      size: 1Gi
    config:
      name: acme
      admins: ["[email protected]"]
      connectors: [vault, schedule]
      safety:
        mode: approval-gated
APPLICATION STATE

Postgres

Provide DATABASE_URL from the instance's deployment secret.

OPERATIONAL SECRETS

OpenBao or assay vault

Select NEUTRON_SECRETS_BACKEND for provider, connection, and capability values.

WORKFLOW STATE

Persistent sidecar volume

Schedules and vault data use the assay-engine volume; the deployment strategy accounts for its single-writer storage.

05

Runtime flow

The Neutron Core agent engine accepts replaceable adapters. Persistence, connectors, and product surfaces remain stable; native tool-governance coverage is adapter-specific.

CLIENTS

Web UI, GitHub and GitLab channels, embedded mode, REST, and token-authenticated MCP.

NEUTRON CORE

Agent resolution, connector policy, approvals, capabilities, provider control plane, persistent traces, and usage.

ADAPTER SEAM

Claude Agent SDK adapter or OpenCode SDK adapter emitting the same normalized agent events.

STATE

Postgres for product state; assay-engine for the encrypted vault, schedules, and durable workflow execution.

PRIVATE BETA

Evaluate the deployment boundary.

Request access with your target Git hosts, identity provider, model providers, and cluster shape.

Request access →Review capabilities