What is Turbobase?
Shipped
Turbobase is an ERP operations and development platform for Oracle NetSuite. Connect your instance and Turbobase mirrors it into a live dedicated Postgres database. This queryable copy of that data allows an operator to diagnose, automate, and build without the traditional performance overhead of NetSuite.
You never install or run anything. Turbobase is a managed service: you sign up at the console, create an instance, and we provision the database, the sync engine, and your Turbobase app for you on dedicated infrastructure.
Who it is for
Section titled “Who it is for”This guide is written for the operator, the person at your organization who signs up, provisions an instance, connects NetSuite, and hands the live app to their team. One operator gets the reach of a whole team of specialists: the platform builds, automates, diagnoses, and manages the instance alongside you. You work entirely through the console at console.turbobase.io.
What you get
Section titled “What you get”When you provision an instance you get:
- A dedicated instance at
<your-slug>.turbobase.app, with its own Postgres database, never shared with another customer’s data. - Live NetSuite sync. Turbobase mirrors your NetSuite records into your instance’s database and keeps it current. Write-back to the source is gated per source and turned on when you’re ready for it.
- Pilot, your AI assistant. Chat grounded in your own data.
- Development in the app. A proposal-and-solution pipeline where you and Pilot shape changes in Studio, then ship them as tracked releases.
- Apps. Internal apps built on your data from a plain-English brief and served inside your instance.
- The Analyzer. An inventory of your NetSuite customizations (scripts, custom fields, workflows, roles, forms) with the risk and improvement proposals that come out of it.
- A knowledge base. A living library of how your business runs that your team searches and that grounds Pilot’s answers.
- Self-service management. Orgs, instances, sources, billing, and usage, all from the console.
- Extensibility. Hooks, conduits, and a marketplace for going beyond the built-in behaviour (see Extending Turbobase).
How it is managed
Section titled “How it is managed”Two surfaces matter to you as a customer:
| Surface | Where | What you do there |
|---|---|---|
| The console | console.turbobase.io |
Sign up, create orgs, provision and manage instances, connect sources, view billing and usage |
| Your Turbobase app | <your-slug>.turbobase.app |
Your team’s day-to-day work with the live data |
The console and the app are separate sign-ins with separate credentials. See Open your app.
Connecting additional sources
Section titled “Connecting additional sources”Turbobase runs on NetSuite and can bring other systems into the same canonical layer. A second source lands in the same Postgres, on the same canonical schema, under the same row-level security, so one query spans NetSuite and everything else instead of a round-trip through each vendor’s API.
- Stripe is live alongside NetSuite, on the same connector contract: webhook-led ingest, canonical projection, and write-back.
- A broader set is registered against that contract and offered in the console: QuickBooks, Xero, Salesforce, Zoho CRM, Shopify, HubSpot, Workday, Dynamics 365 Business Central, Jira, Asana, Notion, GitHub, Zendesk, Intercom, Ramp, Bill.com, GetSales.io, DocuSeal, PrintNode, WhatsApp Business, and the knowledge sources Google Workspace, Fireflies.ai, Granola, FeedHive and Azure Blob Storage. Each is enabled per instance, and Add sources says what each one brings in.
- Atlas consolidates identity across sources, so the same real-world customer seen in NetSuite and in Stripe resolves to one canonical entity rather than two rows.
- Conduits pull from a system that has no connector at all and land the result on the same canonical tables.
- More than one connection of the same source is supported: two NetSuite accounts, two QuickBooks companies, Stripe sub-accounts. Each is its own connection, with its mirrored rows kept apart so records sharing an internal id are never merged.
Standalone instances (no upstream source at all) follow the same contract, with Turbobase itself as the system of record. The schema, RLS, hooks, guardrails, audit log, channels, and app surface are unchanged.
Add sources covers the flow for connecting a source to an instance that is already running.
Next step
Section titled “Next step”Ready to get an instance running? Start with Provision your instance.