Describe workflows, tools, routes, and memory in floyd.yaml—your single source of truth.
Plug in MCP servers (e.g., GitHub), HTTP targets, and vector stores. Secrets stay in our vault.
Lock down egress domains, enforce output schemas, redact PII, and cap per‑session spend.
One command to production. Watch traces, tokens, latency, and costs in real time.
One spec compiles into a managed runtime—routes, memory, retries, and versioning included.
Egress allow‑lists, secret scopes, PII redaction, and JSON‑schema output validation by default.
Per‑session spend caps with kill‑switches, alerts, and model routing to keep costs predictable.
Step‑by‑step traces, token and cost accounting, latency percentiles, and failure triage.
Publish/consume tools via the Model Context Protocol; connect GitHub, internal APIs, and more.
Canary rollouts, instant rollback, and versioned deploys for safe iteration.