Edictum

Setup

Current quickstart for the hosted Edictum control plane.

AI Assistance

Right page if: you want the current public setup flow for the hosted control plane. Wrong page if: you want the local SDK quickstart -- see https://docs.edictum.ai/docs/quickstart. Gotcha: there is no public Docker Compose bootstrap or Railway path right now. The public path is the hosted control plane at app.edictum.ai + api.edictum.ai.

Edictum Control Plane is currently a hosted beta. The public setup path is:

  1. Sign in at app.edictum.ai
  2. Create or select a workspace
  3. Issue an API key in Settings
  4. Start a sample run or connect your own agent
  5. Upload or edit a ruleset in Policies
  6. Watch runs, events, approvals, and audit data in the app

Hosted Quickstart

Issue a workspace API key

Open Settings in the app and create a key for the agent you want to connect.

  • keys use the edk_ prefix
  • the full key is shown once
  • one key per agent keeps revocation surgical

Connect an agent

Python:

from edictum import Edictum

guard = await Edictum.from_server(
    url="https://api.edictum.ai",
    api_key="edk_...",
    agent_id="docs-agent",
    env="production",
    bundle_name="production-rules",
)

TypeScript:

import { createServerGuard } from '@edictum/server'

const { guard, close } = await createServerGuard({
  url: 'https://api.edictum.ai',
  apiKey: 'edk_...',
  agentId: 'docs-agent',
  environment: 'production',
  bundleName: 'production-rules',
})

Go:

guard, err := server.FromServer(server.Config{
    URL:      "https://api.edictum.ai",
    APIKey:   "edk_...",
    AgentID:  "docs-agent",
    Env:      "production",
    Bundle:   "production-rules",
})

Load a ruleset

Use Policies in the app to create or update a ruleset. Agents subscribed to that ruleset fetch it from GET /v1/rulesets/{name}/current and stay current through GET /v1/stream.

Verify the flow

Use these app routes after the agent starts sending traffic:

  • /onboarding for the first connection flow
  • /runs for run summaries and run detail
  • /events for decision events
  • /audit for operator-facing audit activity
  • /approvals for pending and resolved approvals
  • /agents for fleet and per-agent health

Sample Run First

If you want to see the current hosted surface before wiring your own SDK, start with the seeded sample run in the app. That creates a safe workspace-scoped run with real ruleset, event, approval, and workflow data.

What This Page Does Not Promise

  • no public Docker Compose setup
  • no public Railway template
  • no self-serve Stripe billing
  • no public self-hosting wizard

For the live API and transport details, use:

Last updated on

On this page