A real database for your business data. Fast at millions of rows.
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 and counts from a phone.
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 and counts from a phone.
Trusted by frontline employers everywhere
Database speed at any depth
Each table is a real Postgres table, so filters and sorts are SQL with real indexes, not an in-memory grid.
-
Typed columns, real indexes
Text, number, currency, date, dropdown, person and more; mark the columns you sort on for indexing.
-
Saved views with relative dates
"Expiring in the next 30 days" is recomputed server-side every time the view opens.
-
See who changed what
A per-row History panel shows who changed which field, kept 180 days by default.
Two people can count the same shelf at once
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
The server applies it under a row lock, and counts floor at zero.
-
A note on the adjustment
Up to 500 characters explaining why it moved, saved into the row's history.
-
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, and bulk changes run as tracked jobs.
-
Import CSV or Excel
CSV up to 500 MB and Excel up to 100 MB, with each file column mapped before anything lands.
-
Scheduled imports and exports
A nightly pull from a URL, an HTTPS endpoint or an SFTP server, and exports pushed to SFTP.
-
Forms and the REST API
A bound Form adds or updates a row per submission, and the API reads and ingests rows.
Ask for the number, not a guess
The optional agent answers filtered aggregates computed against the real tables, never a guessed total.
-
Counts, sums, averages, min and max
Over every matching row, filtered the way you ask.
-
Relative periods, server-side
A period like "this quarter" is computed server-side.
-
Gated and off by default
Every write asks first, and the agent stays off until an admin turns it on.
Results from teams like yours
Part of OneMango. Add more when you're ready.
The data lives in Power Tables; boards, forms and apps across MangoApps read and write it.
Questions data and ops teams ask
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. One limit follows from that choice and is deliberate — there are no formulas or computed columns. A text, long text, email, URL, dropdown, number, currency or date column can change type in place — to text, dropdown, number or date — keeping every value, and renaming a column is always free.
Pay-as-you-go on rows stored, in packs of 1,000-row units that follow your count — the price per row falls as packs grow. There is no per-seat charge, and archived tables and sample data do not count. 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 on the table's Set up page triggers either on demand, and the last run's status, including failures, shows there.
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 search, or scan a label, to find the row. Adding rows, importing, and exporting stay on desktop, and so does scanning a barcode or QR code into a text column. On a phone, open the full page to use the row editor's scanner.
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 180 days by default — a business admin can set 30 days to 10 years (Admin → Security → Sign-in Policies). 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. While an app is turned on, its records are off the Power Tables row meter — they are included with the app in App Builder.
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 saved-view 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.
Stop switching apps. Start asking.
Every team. Every employee. Every workflow. One people and operations platform — built for the frontline. Since 2008, trusted by 2 million+ users with an NPS of 78.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Prefer to explore first? Ask AI about Typed Data Tables at Database Scale →
- Within one business day: a solutions consultant asks about your workforce and what you run today.
- The demo shows your use case: your sites, your frontline roles, your systems.
- It ends with your price: the package and the price for your employee count, not a generic quote.





























