Frequently asked questions

A board or a table view holds a process until the process gets specific. Bondi generates the model underneath: real tables and relations, permissions derived from the screens people actually use, workflows with typed failures, and an API surface generated from your own schema. You describe the data, the rules, the exceptions and the AI boundaries, and you approve the change set before anything runs.

No, and most teams should not. The common shape is Bondi running the operational layer — the intake, the exceptions, the approvals, the portal — next to an ERP or accounting system that stays the book of record. Be clear about what connecting means: fourteen built-in connectors with typed actions and signed events, an HTTP node, and a published SDK for the system nobody ships a connector for. There is no CRM, ERP or accounting connector and no two-way sync engine, so the pattern that works is one system of record per object, connected deliberately.

Two different sizes of thing. A whole operation — client delivery, orders and inventory, customer onboarding, bookings — built as a system with its own model, screens and roles. Or a single job that currently costs somebody an afternoon: reading the purchase orders that arrive as PDFs, sorting a shared mailbox, generating and sending a document, holding an approval that today lives in a thread. The second kind does not require replacing anything you already run.

Not for the building path. What you do need is someone who understands how the business actually operates and can review the proposed model, rules, permissions and exceptions — because the builder asks where your description leaves a decision open, and an unanswered question blocks the plan rather than being guessed at. Legacy migrations additionally need implementation expertise, and are scoped as a project.

Through a controlled modernization path, one bounded flow at a time, with the rules recovered before anything is rebuilt and a way back from each cutover. That is different from building a new system and is scoped and quoted as an implementation project, separately from the subscription. The assessment can also conclude that replacing is the wrong move.

Start a 30-day trial without a card. The trial begins when you create your first Workspace, and a dedicated database exists from that first workspace. Enterprise and legacy modernization begin with a conversation instead.

Each customer gets a dedicated PostgreSQL database rather than a shared table with a tenant column. Traffic is served over HTTPS/TLS, data at rest carries provider platform encryption, credentials live in an encrypted secrets store separate from the workflows that use them, and backups are kept in a dual-region European archive with public access blocked. The security page states the mechanism and the boundaries rather than an adjective.

Judge it on the mechanisms, not on the assurance. Each environment is its own database; Pro adds Development as a branch of Production with reviewed publishing, version history and version restore; workflow runs are written to your own database, one row per node; and sensitive changes keep an audit history. Contractual uptime targets and service credits exist only under an Enterprise agreement — where there is no contract, there is no SLA, and we would rather say that here.

A paid seat is capacity you purchase and explicitly assign to a linked human user. The organization owner always holds a paid seat. Linked members without a seat are not billed and cannot access organization data. One verified Partner seat is complimentary; additional Partners use paid seats. Invitations reserve a seat only when seat access is enabled. Portal identities, AI Agents, automations, API keys, Service Accounts, and legacy records do not consume paid seats. Paid plans start at three seats.

Automation Runs = max(1, ceil(billable Action count / 20)). Triggers and skipped nodes do not count. Provider calls, per-item work, pagination, retries that reach a provider, and AI tool or model calls count as Actions.

Each additional Production Run costs $0.02 and is deducted automatically from the Wallet. When the Wallet cannot cover another Run, new over-capacity executions pause. An execution already in progress can finish; any uncovered units are recorded without creating debt or a later charge. Monthly Automation capacity packs remain the predictable option for steady usage.

Automation capacity and Bondi-funded AI credit reset on the monthly anniversary of your entitlement start date, even when the base subscription was paid annually. Neither rolls over.

No. Bondi-funded monthly AI credit is consumed first for AI and resets monthly; customer-purchased Wallet balance remains available for additional AI usage and over-capacity Production Runs.

Pro does not impose a portal-count or external-user seat limit. Normal resource quotas, rate limits, acceptable-use rules, and configured permissions still apply. Custom domains and full white-labeling are not currently promised.

No card is required. The trial begins when the first Workspace is created and includes Pro features with Standard resource quotas, $25 of AI credit, and one Workspace. All linked human users can access the organization during the trial. Before converting to a paid plan, an administrator chooses who receives the purchased seats; the owner is always included.

No. Prices are in USD and exclude applicable taxes. Tax is calculated from the billing address and Bondi's tax registrations during checkout and invoicing.

Cancellation takes effect at the end of the paid period. Routine refunds are not offered after purchase; exceptions include an incorrect charge, a legal requirement, or an explicit Bondi decision.

Bondi provides custom database schemas, interfaces, workflows, business rules, role-based permissions, audit history, reporting, APIs, reviewed releases with version restore, and AI steps and agents that operate within defined permissions and rules.

Bondi guides you through the business entities, relationships, process stages, roles, rules, exceptions, and reports involved. It proposes a connected plan for the data, screens, rules and workflows, and applies it only after you approve it. On Pro, you test changes in a Development environment before publishing them to Production.

Bondi has fourteen built-in providers, including monday.com, Stripe, Microsoft 365, Slack, Shopify, PayPal, UPS and Dropbox. A CRM such as Salesforce is not built in: reach it through its API with an HTTP step or publish a typed custom integration with @bondi-labs/integration-sdk. Built-in connectors, HTTP and custom integrations are available from Standard. These are defined actions and events, not a two-way sync engine.

Yes. Every workspace exposes a typed CRUD API with two equivalent surfaces - REST for traditional integrations and GraphQL for typed frontends. Available on Standard, Pro and Enterprise plans for custom integrations and automations.

Yes. Export table data as CSV, read any record through the REST and GraphQL API, and on Pro the workspace owner can take a full SQL export of the entire database. Export access stays open for 30 days after a subscription ends.

Backups are verified and kept for 90 days across two EU regions. They are taken on request and before a workspace is deleted; scheduled backups and point-in-time recovery are not offered today. Removed tables and columns are also archived and protected from purge for 30 days.

Build time depends on the scope and risk of the change. Every change is prepared as a validated plan and shown to you before it applies. On Pro, you test it in Development and publish the reviewed change to Production.