Admin panels
Accounts, plans, entitlements, flags and content over production tables, with role-gated write actions.
Technology and SaaS
The admin panel and ops tooling your product needs, without the sprint
Every SaaS company rebuilds the same things: an admin panel over the production database, a support console across billing and tickets, a churn dashboard. Build them from a prompt or from Claude Code and Codex through the ToolJet plugin, on your real data, inside your SSO and roles. Keep engineers on the product.
- Admin panels over production
- Support and success consoles
- Billing and entitlement tools
Customer consoleAccount · Northwind LogisticsSSOAudit onProduction
PlanEnterpriserenews 14 Nov
Seats active184 / 200+12 this month
Open tickets31 P1 · 41 min
| Event | Actor | When | Status |
|---|---|---|---|
| Seat limit raised to 200 | R. Patel (CSM) | Today 09:14 | Applied |
| Invoice INV-20481 · $48,000 | Billing | 1 Sep | Paid |
| SSO domain added | Customer admin | 28 Aug | Verified |
| Feature flag: agents-beta | Product | 22 Aug | Flagged |
Add an 'extend trial 14 days' action that only success managers can run and logs the reason
Role-gated action and audit note added · awaiting your review
40,000+stars on the open-source core
SOC 2 Type IIISO 27001 and GDPR · Visit the trust centre
Your infrastructureCloud, VPC, on-premise or air-gapped
100+ connectorsplus any REST or gRPC endpoint
Two ways to build
From a prompt on the canvas, or from the coding agent your engineers already use
Product and success teams describe the tool in ToolJet and refine it visually. Engineers build the same apps from Claude Code, Codex or Cursor through the ToolJet plugin, against real data source schemas, and drop into JavaScript or Python where it earns its place. Both write to one application model.
- Real components, queries and permissions, editable on the canvas afterwards
- Agent work lands in development; your release process promotes it
- Data source credentials never reach the browser or the agent
Claude Code
Codex
Cursor- GitHub Copilot
Grok Build
> Build an admin panel on the accounts and subscriptions tables in prod-postgres.
> Success managers can extend trials; only billing can change plans.
list_datasources → prod-postgres, stripe, zendesk
create_app → Admin panel · 3 pages · 14 components
manage_app_permissions → success: extend_trial · billing: change_plan
lint_app_spec → 0 errorsBuilt on the systems SaaS teams already run
PostgreSQL
Stripe
Zendesk
HubSpot
Salesforce
Snowflake
Slack
REST API
What SaaS teams build with ToolJet
Support and success consoles
One screen across your database, Stripe and Zendesk or HubSpot, so support stops asking engineering to look things up.
Billing operations
Invoice exceptions, refunds and plan changes with approval steps and a decision record.
Onboarding and implementation trackers
Per-customer checklists with owners, due dates and status visible to sales, success and the customer.
Churn and health dashboards
Usage, seats and ticket signals from your warehouse, filtered by segment and owner.
Internal request queues
Feature requests, data fixes and access requests with triage, status and Slack updates.
How SaaS teams roll it out
- 01
Connect production safely
Read replicas or scoped credentials for Postgres, plus Stripe and your ticketing tool. Admins connect once; builders never see secrets.
- 02
Build the console
Describe it, or let your engineer's agent build it through the plugin. Set who can read and who can act as part of the build.
- 03
Release like software
Development, staging and production with Git sync and version history. Agent changes wait in development until promoted.
- 04
Hand it to the team that uses it
Success and support refine columns, filters and actions on the canvas. Engineering steps in only for new queries or components.
In production
Teams already running on ToolJet
Built in, not bolted on
The controls your compliance team already expects
Your customers' data deserves the same controls as your product. SOC 2 Type II and ISO 27001 on our side; SSO, query-level permissions and audit logs on every app you build.
Single sign-on and SCIM
SAML, OIDC and LDAP, with directory groups mapped onto ToolJet roles and provisioning through SCIM.
Permissions down to the row
Workspace, app, page, component and query-level access. Row-level security scopes records to the right person.
Audit logs and SIEM export
Platform events with actor, resource and timestamp; configurable retention; export to your SIEM.
Runs where you say
Choose managed ToolJet Cloud or self-host in your VPC, on-premise or air-gapped. Self-hosted Enterprise offers BYOK and private AI deployment options.
Security and governance features vary by plan. Workflows and Agent Builder are available on Self-hosted only; BYOK is a Self-hosted Enterprise add-on. Compare plan availability.
Two ways to get there
Build it yourself, or bring our engineers in
Self-serve
Your team, your pace
Start free. Describe the tool, refine it on the canvas, and ship it under your own access rules. Start with one app, then test it with your team before rolling it out.
Start free
Professional services
Forward-deployed engineers, embedded with your team
When the timeline is fixed or the process is tangled, our engineers build alongside you: scoped delivery, production-ready apps, and knowledge transfer so your team owns the result.
Talk about a projectQuestions SaaS teams ask before they start
Why not have an engineer build the admin panel in our stack?
You can, and every SaaS company does it two or three times. ToolJet removes auth, hosting, permissions and deployment from each tool and keeps the result editable by the team that uses it. Engineers still own the queries and can build from their agent or in code where it matters.
Can it connect to our production database safely?
Yes. Connect a read replica or scoped credentials. Permissions apply per query and per row, so a support console can read accounts without being able to change billing. Credentials stay server-side.
Can our engineers build from Claude Code or Codex?
Yes. The ToolJet plugin exposes your data source schemas, component catalogue and permissions to the agent. It builds native ToolJet apps that land in development and follow your release process.
Does it self-host?
Yes. Docker, Kubernetes, Helm and OpenShift in your VPC or on-premise, alongside ToolJet Cloud. The core is open source.
How is it priced as the team grows?
Pricing is per builder, not per user. Every plan includes an end-user allowance and Enterprise includes unlimited end users, so rolling a tool out widely does not add a seat for every viewer. The pricing page lists the allowance on each plan.
Ship the admin panel this week and keep engineers on the product
See it on your production schema with an engineer, or install the plugin and try it from your agent.
Page updated