Build on Wirebase.
Self-host the whole platform, wire your internal services in through open-standard connectors, and turn workflows into tools your entire team can call.
# Run the whole platform inside your network
$ docker compose up -d
# → app + PostgreSQL, your storage, your model keys
# Wrap an internal service as an MCP connector
# Workspace → Connectors → add your server URL
# Then every team can use it from chat
> @internal-metrics revenue by region, last quarterControl, standards, identity.
Docker
Self-host anywhere
Compose file included; runs on any container platform.
MCP
Open standard
Connectors, not a proprietary plugin system.
SCIM 2.0
IdP provisioning
Plus SAML/OIDC single sign-on.
AES-256
Key encryption
Provider keys encrypted at rest.
Your infrastructure. Your rules.
Wirebase ships as a Docker image with a Compose file that brings up the app and PostgreSQL together — it runs on any container platform, Kubernetes included. Your database, your storage, your provider keys, your network boundary. Prompts, responses, and documents live on infrastructure you operate, and because you bring your own model keys, inference calls go only to the providers you configure — never through a third-party AI gateway. A hosted public REST API is on the roadmap; today, self-hosting gives you the deepest level of access there is.
- Docker image and Compose file, deployable anywhere
- Your PostgreSQL, your S3-compatible storage
- Bring your own model keys — pay providers directly
- No telemetry requirement — your data stays put
Extend with MCP connectors.
Anything you can express as a Model Context Protocol server becomes a first-class tool in Wirebase — available in chat, pinned to agents, and callable from workflow nodes. Write a small MCP server in front of an internal service once, and every team in your organization can use it without waiting on a bespoke integration. Community servers for GitHub, Slack, Postgres, and hundreds of other tools work out of the box.
- Any MCP server becomes tools across chat, agents, workflows
- Wrap internal services once, reuse everywhere
- SSE and Streamable HTTP transports, OAuth built in
- Hundreds of community servers work today
Workflows call your APIs.
Visual workflows include HTTP, Template, and LLM nodes — so a single published workflow can fetch from your internal API, transform the response, reason over it with the model of your choice, and post the result back. Published workflows become callable tools that anyone in the org can @-mention from chat or attach to an agent. Build the pipeline once; surface it everywhere.
- HTTP node calls any endpoint you can reach
- Template nodes shape requests and responses
- Published workflows are @-mentionable tools in chat
- Same workflow reusable from any agent
Built for platform teams.
Self-hosted
Docker image + Compose; runs on any container platform.
MCP native
Open connector standard, not a plugin walled garden.
HTTP + Template nodes
Call internal APIs from visual workflows.
Identity
SAML/OIDC SSO and SCIM 2.0 provisioning endpoint.
Encrypted keys
Provider keys encrypted at rest with AES-256-GCM.
Audit export
Admin and resource actions exportable as CSV or JSON.