PublicViewsCompare
The second copy is the problem.
Not the tool.
Rebuilding an Attio list in Airtable does get you a view you can share. It also gets you two places for every number to be wrong, and a sync in the middle that is now yours to keep alive.
The route is familiar because it works. Sync Attio into a base, build an interface or a portal over the base, share that. People have been doing the same thing over spreadsheets for twenty years.
What it costs is not the subscription. It is that you now own a pipeline. Every attribute your client should see has to exist in two schemas and be mapped between them. Every permission decision is made twice. When somebody adds a field in Attio, the view does not have it until a person remembers.
PublicViews connects to Attio directly. There is no base in the middle, nothing to map, and no second place a record is stored: we cache the attributes your published view needs and nothing else, and Attio keeps the original.
A cached view can be stale too, and we would rather be specific about the difference. Ours goes stale in one direction, for a bounded time, and it says so: every published view carries the time we last got a clean read from Attio, and when a check fails the view tells the viewer we are having trouble reaching Attio and are retrying. A copy in a second database goes stale in both directions, silently, and the fix is a reconciliation rather than a refresh.
- Stage
- Renewed
- Owner
- Dana R.
- Renewal date
- 1 Apr 2027
- Stage
- Renewal due
- Owner
- Dana R.
- Renewal date
- 1 Apr 2026
Side by side
| Rebuild in Airtable | Publish from Attio | |
|---|---|---|
| Where the record lives | Attio, plus a copy in Airtable that has to be kept aligned | Attio. We cache only the attributes your view needs |
| Who maintains the sync between them | You, or a connector you pay for and configure | Nobody. It is the product |
| Adding one attribute to the view | Add the field, map it in the sync, then add it to the interface | Switch it on |
| What a viewer can see | Whatever the base and the interface expose | The attributes you switched on, on the records the filter matched |
| What a viewer can change | Whatever the interface allows, straight into the base | Only attributes you marked editable, held for your approval or applied straight away if you choose |
| Getting that change back into Attio | A second sync, running the other way | Approve it in your dashboard, or let the view apply it for you |
| Time to the first shared view | An afternoon, then ongoing upkeep | Minutes |
| How it fails | Quietly. The two copies drift and nothing tells you | Loudly. A view that could not reach Attio says so on the view |
| Right choice for | An application: logins, roles, several pages, custom logic | Showing a specific slice of a CRM to someone outside it |
No prices in that table on purpose. Any Airtable figure depends on seats, tier and whichever connector you use, and a number we could not source and date would be out of date before you read it. The cost of this route was never the subscription.
One copy, and it tells you how old it is
When the base is the right answer
A comparison page that cannot name a case for the other side is an advertisement. Three cases where the base wins:
- You need an application, not a view. Softr, Stacker and Pory build real applications over a base: logins, roles, several pages, custom logic, file uploads. Jet Admin sits in Attio’s own app store doing the same thing. If that is what the job needs, buy one of those. A published view will frustrate you.
- The data does not live in Attio. If the thing you want to share is half in a CRM and half in a spreadsheet, something has to combine them first, and that something is a base.
- You need to publish a shape Attio does not hold. Rollups across objects, calculated columns, a schema that is genuinely different from your CRM. We publish a list’s records and their direct attributes, one hop, and we are not going to pretend otherwise.
What we are better at is narrower and, for most of these requests, sufficient: showing one specific slice of the CRM you already keep, to somebody outside it, without a second copy in the middle.
Try it against the list you were about to rebuild.
Connect Attio, publish one view free, and see whether the view you get is the one you were going to spend an afternoon building.