FAQ
Short answers about Slab5 as a workspace-native business tool plane, REST API, MCP endpoint, AgentGrid workflow layer, Data & Insights surface, and workspace control plane.
About
Slab5 is a workspace-native business tool plane for apps, AI agents, and repeatable workflows. It combines headless business tools, REST APIs, MCP access, AgentGrid workflows, Data & Insights, audit logs, usage metering, billing controls, and notifications in workspace-scoped environments.
Product
Slab5 includes CRM and CMS modules, but it is broader than either category. It is a programmable business operating layer for apps, agents, workflow automation, reporting, and workspace operations.
Modules
Slab5 includes a headless CRM module — leads, contacts, companies, deal stages, deals, invoices, payments, accounting accounts, and journal entries — but Slab5 is not just a CRM. It is an operational backend with CRM, CMS, tasks, support, assets, integrations, and analytics modules in one workspace, accessible from REST and MCP.
Slab5 includes a headless CMS module with sites, collections, entries, revisions, marketing campaigns, and marketing posts. You can power a marketing site, blog, or product content from it through REST or MCP. Slab5 is not a visual website builder — you render the front end yourself.
Agents
Agents connect through workspace-scoped MCP clients or OAuth grants with explicit scopes. AgentGrid can also run reusable workflows with selected agents, tool allowlists, approval gates, schedules, retries, run logs, usage visibility, and audit context.
AgentGrid is Slab5's workflow control plane for governed AI automation. It supports reusable workflow definitions, agents, tool connections, manual and scheduled runs, approval gates, retries, run history, run logs, and operational visibility.
MCP is the Model Context Protocol — an open standard for exposing tools and resources to AI agents. An MCP server publishes a typed catalog of tools; an MCP client (a Claude or ChatGPT integration, for example) calls those tools on a user's behalf. Slab5 publishes one MCP server per workspace.
Yes, when you grant the credential write scopes for the relevant module. An MCP client with `crm:write` can create contacts; a client with `tasks:write` can create tasks; a client with only `*:read` scopes can only read. You choose the scope set for each agent credential.
Data
Data & Insights is Slab5's reporting and data-product layer. It includes dashboards, reports, datasets, metrics, queries, exports, scheduled artifacts, Object Analytics, Analytics Sites, Custom BI, Workspace Assistant, Data Agents, insights, recommendations, lineage, and knowledge artifacts.
API and MCP
REST is the interface for application and server code; MCP is the interface for AI agents. They operate on the same workspace records, with the same module permissions, audit log, and usage metering. REST keys and MCP credentials carry explicit scopes. Choose REST for traditional integrations, MCP for agent-driven workflows — you can use both at the same time.
Pricing
Slab5 uses a monthly platform plan plus usage-based metering. Plans include unlimited users, workspace limits, included monthly usage, monthly caps, execution capacity, data retention, AgentGrid capacity, Analytics Sites, BI refreshes, and support level. Teams can add prepaid usage balance up to the plan cap and upgrade when they need more capacity or enterprise controls.
No. Slab5 public plans include unlimited users. Usage, workspace limits, execution capacity, retention, AgentGrid capacity, Analytics Sites events, BI refreshes, and support level control platform cost instead of per-seat pricing.
BYOK Developer is the free evaluation plan for developers who want to try Slab5 with their own OpenAI or Claude key. It does not include Slab5 managed AI, keeps lower platform caps, limits recurring workflows to daily-or-slower schedules, and is intended for prototypes and evaluation rather than production operation.
Security
Permissions are enforced at three layers: workspace membership decides whether a user can see a workspace at all; module permissions decide which modules a user, API key, or MCP client can access; and scopes decide which actions a credential can take inside a module. Admin and owner roles gate destructive operations like deleting a workspace or revoking credentials.
Yes. Important actions — credential creation and revocation, membership changes, module configuration changes, workspace settings, and significant record writes — generate audit events. The audit log is workspace-scoped and queryable from the dashboard. You can mirror audit events into external systems via webhook endpoints. Retention varies by plan.
Architecture
No. Slab5 is not a general-purpose database. It is an opinionated operational backend for the business objects most apps already need — CRM, CMS, tasks, support, assets, integrations, analytics. Keep your application database for app-specific state; use Slab5 for operational state that humans and agents share.
Use cases
Yes — in fact, this site is built on Slab5. Use the CMS module to model pages, sections, blog posts, FAQs, and pricing as collections, then render them from your own Next.js, Astro, or Node front end through the REST API. Capture inbound leads into the CRM module in the same workspace.
Beta
Yes. Slab5 is currently in private beta on Shared Cloud. We onboard teams in waves so we can support every new workspace closely. Request access from the homepage and tell us what you want to build — we will follow up.