Internal tools
Internal tools without code, on the data you already have
Every team has a list of small tools it would build if a developer were free: an approvals queue, an equipment register, a helpdesk, an onboarding checklist. They stay in spreadsheets and chat because the queue is never free.
Emberblocks is for that list. Connect the data, describe the tool, arrange the blocks, set roles, publish. The whole thing takes an afternoon and the people building it never pay.
Builders are always free. Facts about other products on this page were last checked on . Tell us if something is out of date: hello@emberblocks.com.
Tools teams build in the first week
Helpdesk
Tickets with statuses, assignees, comments and an SLA formula. Template included.
Approvals
A request form, a manager view filtered to their reports, an approve button, and an email workflow.
Equipment and asset register
Items with QR codes, check-out movements and a who-has-what dashboard. Template included.
HR onboarding
Checklists per new hire, document uploads, due-date reminders. Template included.
Event planning
Sessions on a calendar, vendors on a map, budgets in a chart. Template included.
Admin panel over Postgres
A safe editing surface over production tables with roles deciding who can change what.
How it works
- 1
Connect or import the data
Start on a built-in database, your own Postgres (Supabase, Neon, RDS, anything that speaks Postgres) or an Airtable base, or upload a CSV. Tables and columns are detected.
- 2
Describe the app, or start from a template
Ember drafts tables, views and workflows from a sentence or two. Or open one of ten working templates in the editor without an account.
- 3
Arrange the blocks
Drag tables, cards, record pages, kanban boards, calendars, maps, timelines, charts, stats, forms, buttons, comments, activity feeds, file viewers, signatures, barcodes and embeds onto a grid. Each block reads a table; filters, sorts, groups and formulas are configured in the inspector.
- 4
Set roles and publish
Roles decide which views a user sees and which fields they can read or edit; app users can be loaded from a table in your own data. Every publish is a versioned snapshot you can inspect and roll back, with a stable and a latest channel.
What you get in Emberblocks
Your data, live
Start on a built-in database, your own Postgres (Supabase, Neon, RDS, anything that speaks Postgres) or an Airtable base. Apps read and write live rows, so there are no exports to keep in sync.
Blocks on a grid
Drag tables, cards, record pages, kanban boards, calendars, maps, timelines, charts, stats, forms, buttons, comments, activity feeds, file viewers, signatures, barcodes and embeds onto a grid and wire them to tables. What you arrange is exactly what your team gets.
Real field types
Fields include text, email, phone, URL, number, boolean, date, date-time, time, duration, select, multi-select, reference, multi-reference, image, file, signature, address and JSON. Barcode scanning and signatures work in the browser without a native app.
Workflows
Workflows run when a row is created, updated or deleted, on a schedule, or from a button; steps update records, send email, call webhooks, branch on conditions and run code.
Roles and permissions
Roles decide which views a user sees and which fields they can read or edit; app users can be loaded from a table in your own data.
Publishing like software
Every publish is a versioned snapshot you can inspect and roll back, with a stable and a latest channel.
Phones and offline
Published apps are responsive, install on a phone's home screen, and queue edits made offline until the connection is back.
AI where it helps
Ember drafts a first version of an app from a plain-language description, and end users can ask questions of the data in plain language when you turn it on.
When you need a developer anyway
- The tool needs custom SQL across many tables in one screen, or JavaScript logic on the client. Retool or code fits better.
- The data is not in Postgres or Airtable and cannot be moved or imported.
- You need SSO, audit exports or self-hosting today.
Questions
- How is this different from Retool?
- Retool expects SQL and JavaScript and charges per seat. Emberblocks is configured in an inspector with no code, connects Postgres and Airtable, and never charges builders. See the Retool alternative page for the full comparison.
- Can AI assistants build tools for me?
- Yes. Ember drafts an app from a description inside Emberblocks, and an MCP server lets Claude and other assistants build and query apps from outside.
- Where does my data live?
- Wherever you want it. Use the built-in database, connect your own Postgres so rows never leave your server, or point an app at an Airtable base. Airtable bases are mirrored into Postgres and kept in sync both ways.
- Do I need to write code?
- No. Blocks, a spreadsheet-style formula language and visual workflows cover most internal tools. A run-code workflow step is there when you want it, and an MCP server lets AI assistants build and query apps for you.
- How is Emberblocks priced?
- Builders are always free. Paid plans are priced by the number of people who sign in to your published apps: Starter $29, Pro $79 and Business $199 a month billed yearly. Every new workspace starts with a 14-day Pro trial, no card needed, and there is a free plan after that. Full details on the pricing page.
- What does Emberblocks not do yet?
- Custom domains, SSO and an Enterprise plan are not available yet. There is no live Google Sheets connector (import the sheet as CSV instead). Apps run in the browser and install to the home screen; there are no App Store or Play Store builds.
Try it on your own data.
Every workspace starts with a 14-day Pro trial without a card. You can also open a template in the editor first and sign up only when you want to keep it.