From conversation to
deployed AI workflows
Floprints turns plain-language intent into versioned, governed multi-agent systems on AWS Bedrock AgentCore. Compose, deploy, run, and embed — all in your own AWS account.
Everything you need to ship agent workflows
Design, deploy, govern, and invoke — without building your own agent runtime.
Floprints Composer
Describe goals in natural language. The composer asks clarifying questions, proposes validated plans, and self-corrects on schema errors.
Bedrock AgentCore deploy
Each plan agent becomes its own AgentCore harness with model, system prompt, and tools. Versioned, reconciled, and polled to ready.
Sequential pipelines
Fixed linear steps with explicit input mapping. Deterministic, auditable, repeatable — ideal for regulated processes.
Orchestrator mode
A coordinator agent delegates to specialists, runs independent work in parallel, and pauses for human judgment when needed.
Human-in-the-loop
Runs pause with structured questions. Answers resume the exact harness session — from the console or via the runtime API.
Runtime API
Scoped API keys let external apps list blueprints, start runs, poll status, and respond to human requests over HTTP.
Tools catalog
Built-in Browser, Code Interpreter, and Email Gateway; remote MCP servers; AgentCore Gateway tools — with encrypted credentials at rest.
Audit log
Every admin mutation writes an audit row synchronously. If the audit write fails, the mutation fails — defensible in compliance reviews.
Self-hosted & single-tenant
Runs in your infrastructure with envelope-encrypted secrets, group-scoped provider access, and immutable versioned plans.
How it works
Four steps from intent to a running multi-agent workflow in your AWS account.
Compose
Describe what you want to automate. The Floprints Composer asks clarifying questions and produces a validated WorkflowPlan — agents, tools, models, and execution strategy.
# You: "Review incoming support tickets, # classify urgency, draft a reply, and # escalate billing issues to a human." Composer → proposes 3-agent plan triage → draft → escalation check execution: orchestrator
# Deploy creates one AgentCore harness # per agent, polls to READY, snapshots # tools + transcript into the version. workflow_version: deployed harnesses: triage, draft, orchestrator
Deploy
Each agent in the plan becomes a Bedrock AgentCore harness. Deployment is versioned: draft → deploying → deployed, with full plan and composer transcript captured immutably.
Run
Execute from the console or programmatically. Every step, message, token count, and human pause is recorded. Orchestrator runs can continue across follow-up turns.
POST /api/runtime/workflows/:id/runs # → 202 Accepted, poll for status status: waiting_human questions: [select, multiselect, text, ...]
# Scoped API key in your product Authorization: Bearer bp_... runtime scope → explicit blueprint IDs runtime-all → every deployed blueprint
Embed
Issue scoped runtime API keys so your product can invoke deployed blueprints without console access. Human responses carry attribution for external integrators.
Ready to deploy your first blueprint?
Self-hosted stack, AWS Bedrock AgentCore runtimes, governed from day one.