Conversations
Send up to 500 messages per call, with optional token usage and cost.
Documentation
Install, connect, secure.The essentials to get Blue Falnoa running, connect your agents and review the security model. The full guides come with your licence.
Message usInstall
One Blue Falnoa installation serves one customer. You need a Linux server with Docker, a DNS name, and the version and licence key we send you.
1
Copy the install kit we send with each release to the server.
2
Run the installer with your version, domain and administrator email. HTTPS is automatic.
3
Sign in, open Settings, Licence, and paste the key we return. Until then the app is read-only.
sudo ./install.sh --version <version> \
--domain blue.example.com \
--admin-email [email protected]Everyday operation uses the bf command: status, logs, backup, restore and upgrade, with automatic rollback if an upgrade is unhealthy. Behind your own proxy, or with no internet, there are options for both.
API and SDKs
Agents send their conversations with an ingest key created on the agent’s settings. Messages with an id are safe to retry.
POST /api/agent/v1/conversations/{id}/messages
Authorization: Bearer bfa_…
{ "messages": [
{ "id": "m1", "role": "user", "content": "Where is my order?" },
{ "id": "m2", "role": "assistant", "content": "It ships tomorrow." }
] }Send up to 500 messages per call, with optional token usage and cost.
Agents search the published knowledge over the same API.
Agents that speak the A2A protocol run workflow steps and report back.
Scoped, expiring and revocable tokens for your own automation.
Official clients for TypeScript and Python, with no runtime dependencies.
import { AgentClient } from "@blue-falnoa/sdk";
await new AgentClient(url, "bfa_…").sendMessages("c1", [
{ id: "m1", role: "user", content: "Hello" },
]);Security
A short view of the controls that exist today. The full list, with what is verified and what is not, is on the trust page.
Administrator, operator and viewer roles, enforced on the server.
Authenticator app, recovery codes, passkeys and OpenID Connect.
Passwords, session and API keys are stored hashed; credentials are encrypted.
A hash-chained audit log you can verify and export.
One instance per customer, in a locked-down container.
In production it refuses to start with an unsafe configuration.
Found a vulnerability? Report it privately by email. Please do not open a public issue. hello@falnoa.com
Read the trust pageAsk and we send them.Licensed customers receive the deployment, operations and security guides. Ask and we will send what you need.
Message us