Replace your stack. Run on one runtime.
Your business runs on dozens of disconnected SaaS tools. Overlapping, ungoverned, billed per seat whether you use them or not. rcrt runs the work those tools do on a single governed runtime: agents with persistent memory, sandboxed tools, and connectors to the systems you keep — secure, auditable, and priced on what you run.
You are paying for sprawl, not value.
The average enterprise runs hundreds of tools that overlap, barely integrate, and quietly leak budget. The bigger cost is not the licences. It is the work nobody can govern, the data nobody can join up, and the AI nobody can see.
Unused licences
Seats paid for and never used, across tools with duplicate functionality you already own somewhere else.
Integration tax
The recurring cost of wiring disconnected systems together, only to have them break with the next update.
Ungoverned risk
Shadow AI: teams pasting company data into tools nobody approved, with no audit trail and no way to prove compliance.
Figures are typical industry consolidation benchmarks, not rcrt measurements. Your number comes from a discovery session against your contracts.
Not another app. The runtime underneath them all.
rcrt is infrastructure: an agent and context runtime that executes complex, multi-step work across your systems with governance, security and repeatability built in. Everything in it is a breadcrumb — one universal, tagged, searchable unit of data. Tools become agents. Agents run on one engine you control.
Your systems, one context
Every record, action and document becomes a breadcrumb: tagged, versioned, embedded and searchable, joined up across what used to be silos. 18 first-party connectors today — and a new one is a definition you write in minutes, not a vendor integration you wait for.
Agents and people, together
Agents with Level-of-Detail memory run the work your SaaS tools used to do — context assembled in 50–200ms per turn — with humans approving every action where judgement matters.
Audited by default
Row-level tenant isolation, role-based access, sandboxed tool execution with per-tool permissions, and a trace on every context assembly. Sovereign deployment on your own cloud project.
Production, not pilots
Model-agnostic across 300+ models via one address — Vertex AI, Anthropic, OpenAI, Google and the full OpenRouter catalogue — switchable per agent, fail-loud, no silent fallbacks. Priced on what you run, not seats you forgot you bought.
This is not a diagram. Every point is a real breadcrumb in a live rcrt workspace — 475 of them here: 49 tools, 11 agents, 33 knowledge docs, 24 services and 358 messages — positioned by their embeddings in semantic space. Agents navigate this space every turn; the LOD engine renders what's near in full detail and compresses the rest.
A CRM in one session, not one quarter.
This is RCRT Studio — the real app, replayed: describe the product, watch the builder agents connect services, compose tools, agents and knowledge as breadcrumbs, wire the frontend, and deploy. Scripted animation of the real build loop — not a mock-up of features we don't have.
Scripted replay rendered in the real Studio interface — chat, build plan, backend inspector, live preview, deploy. Book a session to watch it live on your own use case.
What could rcrt replace?
The 2026 SaaS Market Map covers the 316 tools across 41 categories that make up most business stacks. Pick what you run, then let the advisor respond — with rcrt's JIT UI, not a chat box. Every answer is a card you can act on.
Tell us what you run
Tick a category, or expand it and pick exact tools. Each tool carries the map's lens: replace, or keep-and-integrate.
"discovery" means the map doesn't pre-judge that tool — whether rcrt replaces it is confirmed against your usage in a discovery session.
cards.resolve() powers in production.Five tools, one runtime.
A leading Australian clinic group (NSW + VIC) ran their growth engine across a CRM, a bookings platform, call-centre telephony, website lead forms and a broken ad stack. rcrt is consolidating all of it into one Growth & Bookings Hub.
$31k/month of paid search, 28 cents back per dollar.
23+ broken and duplicate conversion actions meant Google's bidding optimised to noise. No system could join an ad click to a booked consultation to revenue. Five disconnected tools each held a fragment of the answer.
A Growth & Bookings Hub with an advisor that acts.
Leads, bookings, campaigns, attribution and customers — all breadcrumbs on one runtime. A growth-advisor agent generates ad creative, reallocates budget, applies negative keywords, exports conversions, creates bookings and advances deals. Every action human-approved.
Three products already run on it.
rcrt is not a deck. A chat-to-app builder, an MSP business cockpit and a 34-bundle marketplace all run on the same runtime — the one this page is selling.
The builder you just watched
The CRM assembling in the replay above is Studio doing its actual job: describe an app in plain language, agents compose the backend as breadcrumbs, you inspect the code, deploy to Cloud Run, and share a time-limited preview link — QR to phone included.
Run customers as a managed-intelligence provider
The cockpit MSPs use to run customers on rcrt: opportunity radar, fleet provisioning, guardrails with human approval, model backtests that replay real conversations against cheaper models, margin-aware billing, and a white-label customer portal.
34 bundles today. Yours in minutes.
Personal assistants, inbox triage, meeting minutes, SOP knowledge bases, support concierge, sales outreach, construction PM, quarterly business reviews — each a versioned unit of agents, tools, knowledge and services that installs in one click. Composing a new bundle for your business takes minutes, not a project plan: publishing is a definition change, not a service deploy.
One typed SDK. This page runs on it.
@possibl/rcrt-sdk is the developer surface: isomorphic TypeScript for browser, Node 18+ and React Native. One client for agents, streaming, approvals, files and multi-workspace fan-out. Bring your own identity provider — the SDK never dictates one. The live advisor in the calculator above is built with it.
Agents, streaming, approvals
Everything is a breadcrumb — chat, memory, pending actions. One CRUD surface underneath it all; actions gate on a human tap.
import { RcrtClient, staticTokenProvider, CardsModule } from '@possibl/rcrt-sdk';
const rcrt = new RcrtClient({
apiUrl: RCRT_API,
tokenProvider: staticTokenProvider(WORKSPACE_KEY), // tk_*
});
// chat with an agent, stream the reply
const { session_id } = await rcrt.chat.send({
message: 'Summarise my inbox',
target_agent: 'crm-advisor',
});
rcrt.chat.sessionStream(session_id, {
onDelta: ({ delta }) => ui.append(delta),
onMessage: (bc) => {
if (bc.tags.includes('interpret:pending-action')) {
ui.card(CardsModule.extractCard(bc)); // human approves
}
},
});Multi-tenant by default
Platform → org → workspace isolation enforced at the row level. Fan out across a fleet without ever mutating one client's tenant.
// a console over dozens of workspaces,
// each client permanently bound to its tenant
const reports = await Promise.all(
workspaces.map((ws) =>
rcrt.forTenant(ws.tenantId)
.marketplace.listInstalledBundles(),
),
);Also on the runtime: an MCP server exposing your workspace tools to Claude Code and other MCP clients, and cross-org agent federation with @org addressing.
Not a workflow. Not a chatbot. Not a wrapper. The runtime.
Workflow tools automate steps you draw. Chatbots reply and forget. Vibe-coding writes an app and leaves you to run it. rcrt is the layer underneath all three: agents with durable memory doing real work under real governance — on a runtime that composes whatever's missing. What Supabase was to the interactive web, rcrt is to the AI era.
The database was the backend. You built pages on a relational core.
Auth, data, realtime and storage behind one SDK. Backend as a service.
Memory, agents, tools and governance behind one SDK. The agent runtime.
The database made the web. The backend-as-a-service made mobile.
The agent runtime makes the AI era.
Workflows become things agents draw. Chat becomes one surface among many. Apps become things it builds. The runtime is the product.
See your real number. Book a session.
Bring your stack and your contracts. In one discovery session we will map what rcrt consolidates, what it cannot, and the saving you can take to your board — priced on what you run, not seats you forgot you bought.
Book a Possibilities Session