A Real Database For Your Business Data
Power Tables gives every dataset its own real Postgres table inside MangoApps — a parts catalog, sales ledger, or asset registry that scales to millions of rows, stays fast, and counts from a phone.
What Power Tables Helps You Do
The data backbone for the numbers your teams run on — stored at database scale, queried at database speed.
Store Data At Real Scale
Each table you create is a real Postgres table with typed columns — text, number, currency, date, select, People, and more. Scale is bounded by indexes, not by how much a browser can hold.
Import CSV Or Excel
Bring in CSV files up to 500 MB and Excel workbooks up to 100 MB with an explicit column-mapping step, streaming progress, and per-row error reporting. New file columns can be created automatically as you import.
Count Stock Without Typing
Mark a number column as a counter and it becomes − / + buttons on desktop, in the row drawer, and on a phone. Each tap sends the change, not the answer, so two people counting the same shelf both get counted.
Author Saved Views
Capture a filter, sort, and column layout straight from the grid. Every table starts with an "All rows" view — and views are what Live Boards bind to.
Filter By Relative Dates
Save a view as "expiring in the next 30 days" and it recomputes server-side every time someone opens it — today, this week, this month, this quarter, this year, last N days, next N days.
Enforce Validation Rules
Required values, min/max bounds for numbers and currency, regex format patterns for text — enforced on every row write, including per-row on imports and the REST API.
See Who Changed What
Every single-row change lands in a per-row History panel — who changed which field, old value to new — kept for 180 days. A count adjustment can carry a short note ("used in OR 2") that rides the same trail.
Get Data Back Out
Export any view to CSV or Excel — current filters, search, sort, and visible columns — as a background task with a download when it's ready. Or integrate over the REST API.
Four Reasons Teams Move Their Data Into Power Tables
Why operational datasets outgrow spreadsheets — and what a real database inside the workspace does differently.
Database Speed At Any Depth
Filters and sorts are SQL with real indexes. Pagination is keyset-based, so page one thousand is as fast as page one, and row counts come back as fast estimates instead of blocking scans.
- One Postgres table per user table — SQL-native sort and filter, no in-memory grid ceiling.
- User-marked indexes — mark the columns you sort and filter on; index builds run in the background with tracked progress.
- Keyset pagination — constant-time scrolling with no row-count ceiling.
- Full-text search across text columns, plus per-column filters with type-aware operators.
- Relative date windows — today, this week, this month, this quarter, this year, last N days, next N days, recomputed server-side every time the view opens.
Two People Can Count The Same Shelf At Once
Mark a number column as a counter and it stops being a typed field — it renders − / + buttons in the desktop grid, in the row drawer, and on a phone, where they work without JavaScript. A tap sends the change, not the answer, and the server applies it under a row lock.
- Simultaneous counts both land — a shelf holding 12 with two people each tapping − at the same moment ends at 10, never 11. Counts floor at zero.
- A note on the adjustment — up to 500 characters explaining why it moved, saved into the row's per-field history.
- Barcode and QR scanning from a phone camera into text columns, with typed fallback — Code 128, Code 39, EAN-13, EAN-8, UPC-A, QR.
- Crossing zero can fire a rule — an automation tells someone to reorder instead of waiting for the next stock-take.
Data In And Out On Its Own Schedule
Recurring exports from a POS, ERP, or telephony system land automatically, bulk changes run as tracked jobs, and templates get new tables started on structure.
- Scheduled imports — one nightly pull per table, in replace or append mode, from a public https URL, a credentialed HTTPS endpoint, or an SFTP server, with a Run now button.
- Scheduled exports — pushed to an SFTP destination on a schedule; an export has to push somewhere credentialed, so SFTP is the only destination.
- Forms bind to a table — append mode adds a row per submission, update mode matches an existing row on a chosen column and updates it, which is the stock-take pattern.
- Bulk edit — set one column's value across selected rows as a tracked job with per-row validation errors reported.
- Prebuilt templates — Asset registry, Visitor log, Store performance, and Incident tracker schemas in the New Table drawer.
- REST API — list tables, read rows with keyset pagination, run filtered aggregates, and ingest rows under least-privilege token scopes.
A Database, Not Another Spreadsheet
Editing is deliberately record-oriented — click a row and a drawer opens with one typed input per column, with optimistic concurrency so two admins never silently overwrite each other. AI Sheets is the spreadsheet product; Power Tables is where big, structured data lives.
- Typed inputs per column — date pickers, dropdowns, yes/no, a people picker.
- Optimistic concurrency — conflicting saves are caught, never silently overwritten.
- Columns in use can't be archived — a column an automation rule, a Live Board, or a bound Form depends on is refused, and the refusal names what is using it. Renaming is always free.
- Ask AI aggregates — the optional agent answers filtered counts, sums, averages, minimums, and maximums directly from your tables, over a relative period it computes server-side.
- Feeds Live Boards — saved views power always-current leaderboards, stat tiles, and tables on dashboards and signage.
Power Tables In Practice
A practical scope check: what the app covers, which controls matter, and the workflows teams usually run first.
Core workflow
Admins create typed tables and author saved views; contributors add and edit rows; everyone else with app access can view, filter, and search.
Controls that matter
Per-column validation rules, per-row change history, per-table sharing, refusal to archive a column something depends on, and least-privilege API token scopes.
Scope and specs
Useful specs: 12 column types; up to 10 million rows per table; CSV import up to 500 MB and Excel up to 100 MB; row history kept 180 days.
Count supplies from a phone
Tap − as items are used and scan the barcode to find the row. Mobile is read and count; adding rows, importing, and exporting stay on desktop.
Sales ledger behind the leaderboard
Import a weekly sales extract, save a "top sellers" view, and bind a Live Boards leaderboard to it.
Equipment and asset registry
Serial numbers, locations, warranty dates, and cost — filtered to "warranty ends in 90 days" as a shared view.
Searchable reference table
A parts catalog or price list with hundreds of thousands of rows, instantly searchable by everyone with app access.
Stock-take through a bound Form
Point a Form at the table in update mode — each submission matches an existing row on a chosen column and updates it, instead of piling up rows.
PAY AS YOU GO
Pricing That Follows The Data, Not The Headcount
Power Tables is available to every tenant and stays off until an admin enables it. No license decision, no per-seat negotiation.
Metered on rows stored
Billing is pay-as-you-go per 1,000 rows stored per year. Store more, pay more; archive a table and it stops counting.
No per-seat charge
Every member with app access can view, filter, and search tables — viewers are never a line item, and there is no monthly floor.
Volume tiers that reward scale
$1.20 per 1,000 rows per year for the first 1 million rows, $0.36 per 1,000 to 10 million, and $0.24 per 1,000 above that — the millionth row costs less than the first.
Trials and archives are free
Sample data doesn't bill, and an archived table stops counting against the meter — so evaluating the app and retiring a dataset both cost nothing.
Connected To The Rest Of MangoApps
→ Live Boards
Boards bind to Power Tables saved views — the data lives here, the always-current leaderboards, stat tiles, and charts render there.
→ AI Sheets
AI Sheets is the spreadsheet — cell editing and formulas. Power Tables is the database. Work a dataset in Sheets; store one at scale here.
→ Digital Signage
Via Live Boards, saved views become signage slides — the break-room leaderboard updates as imports land.
→ App Builder
Mini Apps are authored in App Builder and run on Power Tables — the app's data is a table, its tabs are saved views, its behavior is automation rules. Their rows bill on this same meter, not a second charge.
→ Forms
Bind a Form to a table so each submission becomes a typed row — append mode adds a row per submission, update mode matches and updates one.
→ Ask AI
The optional Power Tables agent answers filtered counts, sums, averages, minimums, and maximums directly from your tables — off until an admin turns it on.
Pair Power Tables With Its Agent
The Power Tables agent answers data questions with filtered aggregates computed against the real tables — never a guessed total.
Power Tables
Filtered counts, sums, averages, minimums, and maximums over any table.
Customer Success
How Teams Use MangoApps For Operational Data
Video Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Frequently Asked Questions
AI Sheets is the spreadsheet — cell editing, formulas, in-memory richness. Power Tables is the database — typed records, millions of rows, saved views, and no formulas. The grid is a read-only viewport and edits happen record-by-record in a typed drawer. Use Sheets to work a dataset; use Power Tables to store one at scale and feed live displays. Two limits follow from that choice and are deliberate — there are no formulas or computed columns, and a column's type is fixed once created, so add a new column with the right type instead. Renaming a column is always free.
Pay-as-you-go on rows stored — $1.20 per 1,000 rows per year for the first 1 million rows, $0.36 per 1,000 to 10 million, and $0.24 per 1,000 above that. There is no per-seat charge and no monthly floor, and archived tables and sample data do not bill. The app is available to every tenant with no license decision — it simply stays off until an admin enables it.
There are three app-level tiers. Administrators create tables and define columns, contributors add and edit rows, and everyone else with app access can open tables, filter, sort, and search — viewing is not an admin privilege. On top of that, each table is shared individually. Leave it open to everyone with app access, or mark it restricted and name its audience by granting specific people or groups viewer, contributor, or manager rights, each with an optional expiry. A grant on a restricted table can raise someone to contributor for that one table without giving them the app-wide tier.
Yes to both. Import accepts CSV files up to 500 MB and Excel (XLSX) workbooks up to 100 MB through a two-step flow where you map each file column to a table column, create it as a new text column, or skip it before anything lands. Export captures the grid's current view — filters, search, sort, and visible columns — as CSV or Excel, running as a background task with a download when it's ready; Excel export is capped at 100,000 rows and CSV has no cap. For programmatic access there is also a REST API.
Yes, in both directions. Each table can have one scheduled import — a nightly pull in replace mode (the source is the system of record) or append mode (every run adds rows). The source can be a public https URL with no setup, a credentialed HTTPS endpoint, or an SFTP server; protected sources bind to a connection an admin configures once at /admin/integrations. Each table can also have one scheduled export, which pushes the file to an SFTP destination — SFTP only, because an export has to push somewhere credentialed. A Run now button triggers either on demand, and the last run's status, including failures, shows on the table page.
Yes, and that is the point of counter columns. Mark any number column as a counter and it stops being a typed field — it renders − / + buttons in the desktop grid, in the row drawer, and on a phone, where they work without JavaScript. A tap sends the change rather than the answer, and the server applies it under a row lock, so if a shelf holds 12 and two people each tap − at the same moment the result is 10, never 11. Counts floor at zero, and crossing zero can fire an automation so someone is told to reorder. Each adjustment can carry a short note explaining why it moved.
Read and count. Mobile shows table cards and searchable row cards, and counter steppers work there without JavaScript, so a stockroom or clinical team can tap − as items are used and scan a barcode or QR code with the phone camera to find the row. Adding rows, importing, and exporting stay on desktop.
Yes, for single-row changes. Every add, edit, and delete made through the row drawer, bulk edit, or the REST API is logged per field — who changed it, old value to new — and shown in a History panel inside the row's edit drawer, kept for 180 days. A note attached to a count adjustment rides the same trail. Imports and bulk inserts are deliberately not logged row by row; the import task record is the audit trail there.
No, and that refusal is the feature. A column referenced by an automation rule, a Live Board, or a bound Form cannot be archived out from under what is using it, and the refusal names each dependency so you know what to change first. Renaming a column is always safe, at any table size.
Yes — that is what Mini Apps are, and they are authored in App Builder rather than here. An admin describes what they need in plain language and gets a real app at its own address, with its own name, icon, and place in the sidebar. Underneath, it runs on Power Tables — the app's data is a table, its tabs are saved views, its behavior is automation rules, and its dashboard is a Live Board. Because it is a real app it carries its own permissions, so a frontline user can be given one narrow door (report a count for one item) without being able to browse the table behind it. Mini Apps stay private to your tenant and their rows bill on the same Power Tables row meter.
No — that is the point of the architecture. Each table is a real Postgres table, so filters and sorts are SQL with real indexes, pagination is keyset-based, and row counts are fast estimates rather than blocking scans. You mark the columns you sort and filter on for indexing, and index builds run in the background.
A saved view captures a filter, a sort, and a set of visible columns — authored straight from the grid, and every table starts with an "All rows" view. Live Boards bind to views, not raw tables, so the view defines exactly which rows and ordering a leaderboard or stat tile reflects. Refine the view and every board on it updates.
No, because a date filter can be written as a relative window rather than a fixed range — today, yesterday, this week, this month, this quarter, this year, last N days, or next N days. The window is recomputed server-side every time the view is opened, so "expiring in the next 30 days" keeps meaning that instead of freezing to the day it was saved. The same vocabulary drives Live Boards periods and view-watch alerts, so a board, an alert, and the grid all agree on what "this quarter" means.
Yes. The REST API under /api/v1/power-tables lists tables, returns a table's structure (columns and views), reads rows with the same filter grammar and keyset pagination as the grid, runs filtered aggregates (count, sum, avg, min, max), and — for contributor users and above — ingests rows one at a time through the same casting, quota, and validation path as the row drawer. Access is by API token with least-privilege scopes — read:power_tables for reads, write:power_tables plus Power Tables contributor rights for writes. Updating and deleting rows are not exposed.
No, deliberately. Power Tables stores and serves typed data; it does not compute derived cells. For formula work, that is AI Sheets' job — and for display-time math like trends, Live Boards can compare two numeric columns of the same view.
Let's Talk
Since 2008, we've been building the employee platform for the frontline, earning the trust of 2 million+ users and an NPS of 78.
Why Choose Us?
- Frontline AI: Governed AI for every employee and workflow.
- Top Security: HITRUST, ISO & SOC 2 certified.
- Exceptional UX: Delightful on mobile and desktop.
- Proven Results: 98% customer retention rate.
Trusted by 1,000+ leading workforce organizations:
Prefer to explore first? Ask AI about Typed Data Tables at Database Scale →