The grid componentNot another app to buy seats for.
Rowhouse is a part of the platform you place on a Lightning page, not an application you buy seats for. Users edit records in place with spreadsheet keys, add new ones at the top, group and total them, show and edit a related record’s fields, open related records under each row, import and export, and run actions. Admins build each grid on a tab in Salesforce, without code.
The component, not the app
One component, Rowhouse Grid, goes on any App, Record or Home page in Lightning App Builder. Which grid it shows is a single setting: the name of a grid you built. The same grid can sit on several pages and change in one place, because its behavior lives in metadata rather than in page properties.
Two things that are hard to copy
The cell editors. Ten of them, covering every editable field type. Salesforce’s own data table has no editable type for lookup, owner, multi-select picklist, dependent picklist, time or long text; Rowhouse edits all of them in the cell. Rich text stays read-only.
Configuration as metadata. Every grid is Custom Metadata — seven types, from the grid itself to its columns, display rules, filters, actions and child tables. Build in a sandbox, move it to production in a change set, keep it in source control. An upgrade cannot overwrite it.
Who it is for
Admins build grids on the Grid Admin tab or in Setup, with no code, and place them on any page. Users in sales, service, account management and operations change many records at once with spreadsheet keys, copy and paste, undo, grouping and totals, instead of exporting to a spreadsheet and importing back. Developers get the Apache-2.0 source, a published benchmark with its script, published limits and configuration they can keep in version control.
See it as your users will
How a grid is put together
One component on any App, Record or Home page names a grid; the grid’s configuration is Custom Metadata in your org; and every read and write goes through Salesforce’s security as the person using it.
A pipeline review, without leaving the list
Grouped by stage in the picklist’s order, a sum of amounts per stage and in total, overdue close dates in red and big deals in green — all of it set on the Grid Admin tab.
The life of an edit
Type, keep, save: changes wait on the Save bar, go to Salesforce in batches of 200 with your own rules running, and come back with formulas recalculated.
Related records under each row
Open a row and its related records appear as tabs, each a full grid with its own Save bar, three levels deep.
The grid component: questions
Where does Rowhouse run?
On Lightning Experience App, Record and Home pages. It does not run in Salesforce Classic or in Experience Cloud sites, and it has not been tested in the Salesforce mobile app. On narrow screens and phone browsers it shows records as cards.
Does my data leave Salesforce?
No. Every Rowhouse read and write runs inside your org as the user, through Salesforce’s own object, field and sharing security. There are no callouts and no outside services. Files leave only as CSVs a user downloads in their own browser.
Is it really free?
Yes. Rowhouse is Apache-2.0 open source with no paid tier, no feature gates and no upsell in the product. Help is free too.
Where is the documentation?
Inside the app. The Grid Guide tab holds the user guide, five tutorials and the configuration reference, one click from every grid, and always matches the version you installed.
Three things you can verify without asking us
Free. Not freemium, not a trial, not a tier.
Install it, assign the permission sets, build your first grid on the Grid Admin tab. Everything else is in the Grid Guide inside the app.