FAQ
Short answers on act runs, billing, account access, and security. Each topic links to the spine guide for detail.
Use this page when you need a fast answer before opening a full guide. Billing questions below match Billing & limits so the answers stay consistent.
Product and act
- What is Blekline?
- AI workflow execution infrastructure. Your stack keeps infer and decide; Blekline governs act where tools run and side effects happen. See Documentation home.
- Do hooks and MCP require a workflow run?
- Hooks and MCP can enforce published policy on ingress without a run row. Workflow runs are the identity you meter, audit, and operate as a unit in Production. See Connect agents and clients.
- What is compileHash?
- Fingerprint of the published runtime policy bundle captured when a run is created. Audit and run detail use the same hash. See Runtime policy.
Workflows and runs
- How do I start my first act run?
- Register a workflow, publish policy, and POST a cell run or use the Runs console. See Run first workflow.
- What does pending mean?
- The run row exists and a cell Job is scheduling or awaiting assign on hosted or cluster paths. See Run lifecycle.
- Hosted act vs cells in my cluster?
- Platform Team uses hosted runtime. Platform Production runs act in cells in your VPC with a connected cluster. See Spin up cells.
Billing and limits
- Why not price per engineer?
- Connected agents are a flat cap per workspace, not a seat SKU. A 20-person team on Platform Team pays $499/mo, not per developer.
- What happens when I hit the act run-minute cap?
- New act runs return a quota error until the UTC month resets or you upgrade. Enable pay-as-you-go overage in workspace billing when your plan supports metered act run-minutes. See Billing & limits.
- Do failed runs count?
- Terminal runs with no recorded duration bill 1 minute. Short successful runs bill actual duration (minimum 1 minute). See Run lifecycle.
- Local tier?
- Blekline Local stays free for hooks and stdio MCP. Hosted act runs require Platform Team or higher.
Account and access
- Workspace token vs API key?
- Session auth in the browser uses your workspace session. Automation uses scoped workspace tokens from API keys with explicit capabilities. See API keys.
- Where do I change plan or payment?
- Workspace owners manage billing, spend caps, and invoices in Workspace billing. See Workspace billing.
Operations
- A run is blocked. What now?
- Blocked means governance stopped the path. Review Event History on the run, then rule approvals or threat signals when your role allows publish. See Threat signals & approvals.
- Where is proof for an incident?
- Audit log and execution metrics filter by compileHash, run id, and time range. See Audit & metrics.
Security and data
- Does Blekline store prompt bodies in audit by default?
- Audit is metadata-first by default. Mask and ingress handling follow your published policy; see Security for honest residency boundaries. See Security.
- Is hosted mask zero-knowledge?
- No. Hosted mask evaluates content under your policy. Trust boundaries and tiers are documented on Security. See Security.
OSS and control plane
- What is open source vs the app?
- Integrator packages (client, MCP, contracts) ship on npm and GitHub. The managed control plane, billing, and production cells are at app.blekline.com. See blekline-oss on GitHub.