Pottr is the database layer WordPress never shipped. Build directories, portals, and booking systems — without moving your client off the platform they know.
Built for agencies and freelancers who've hit the ceiling with
and Custom Post Types.
Limited to 10 spots.
Sound familiar?
You've been here before. Client wants WordPress, you want to build something real,
and somewhere in the middle you're debugging a meta_query
that has no business being this slow.
At 50,000 entries, that's a million rows in
wp_postmeta
— all being scanned every time someone hits your API.
Built for content editors, not developers. Parsing them on the frontend is a tax you pay on every request.
You either pollute
wp_users
with customer accounts or bolt on a third-party solution that wasn't designed for this.
Another plugin, another point of failure, another thing to debug at 11pm before a client launch.
What is Pottr?
It replaces the way WordPress stores and serves your custom data — from the ground up. You define your schema in the admin. Pottr handles the rest. What your clients experience doesn't change. What you ship does.
Without Pottr
// 20 fields × 50,000 entries
// = 1,000,000 rows in wp_postmeta
// scanned on every API request
SELECT * FROM wp_postmeta
WHERE post_id = 123
AND meta_key IN (
'title', 'description', 'status',
'price', 'location', 'category'
/* ...14 more */
);
With Pottr
// 50,000 entries
// = 50,000 rows in wp_pottr_entries
// one indexed query
{
"id": "86",
"title": "Midnight",
"status": "active",
"price": 49,
"location": "London",
"category": "design"
}
What it ships with
Pottr ships five things agencies have been cobbling together from plugins, custom code, and prayer.
Your data, at scale.
Built for the projects where WordPress usually taps out. Directories. Portals.
Marketplaces. Pottr handles the kind of data volume that makes WP_Query
sweat.
An API you'll actually enjoy consuming.
Every collection you create gets its own dedicated REST endpoint — clean, fast, and ready for any frontend. No parsing. No bloat. Just the data you asked for.
Your data, in motion.
The moment something changes in WordPress, Pottr can tell the world. Zapier, Make, your own service — no plugin required, no polling, no delay.
App users. WP Admins. Never the same list.
Building a customer portal? Pottr ships its own auth system — completely separate from WordPress users. Your clients stay admins. Your customers stay customers.
Your server. Your data. Zero SaaS fees.
Everything Pottr stores lives on your client's existing WordPress server. No third-party database. No monthly infrastructure bill. No vendor to negotiate with.
The killer differentiator
Your client will never log into Supabase. They won't manage a database table they don't understand. With Pottr, you ship a modern, API-driven app — and your client still just logs into WordPress. The thing they've always known.
Limited spots. No spam. One email when it's ready.
What you can build
Built for the projects that push WordPress to its limits — and then some.
App users stay completely separate from WP Admins. Clean auth, clean data, clean handoff.
Filter and serve thousands of entries in one clean API call. No timeouts. No workarounds.
The moment a slot is booked, Pottr fires a webhook. Your automations take it from there.
Collections isolate workspaces naturally. Ownership is enforced automatically.
Your client manages content in WordPress. You consume clean, structured data on any frontend.
App users stay completely separate from WP Admins. Clean auth, clean data, clean handoff.
Filter and serve thousands of entries in one clean API call. No timeouts. No workarounds.
The moment a slot is booked, Pottr fires a webhook. Your automations take it from there.
Collections isolate workspaces naturally. Ownership is enforced automatically.
Your client manages content in WordPress. You consume clean, structured data on any frontend.
App users stay completely separate from WP Admins. Clean auth, clean data, clean handoff.
Filter and serve thousands of entries in one clean API call. No timeouts. No workarounds.
The moment a slot is booked, Pottr fires a webhook. Your automations take it from there.
Collections isolate workspaces naturally. Ownership is enforced automatically.
Your client manages content in WordPress. You consume clean, structured data on any frontend.
Questions
Yes — Pottr is a self-hosted, WordPress-native backend-as-a-service. It gives you the REST API, auth system, webhooks, and structured data layer you'd expect from a cloud BaaS like Firebase or Supabase, but everything runs on your client's existing WordPress server. No SaaS fees. No external database. No vendor lock-in.
Not yet — but it goes further. Pottr gives you custom tables with real relationships,
typed fields, and versioned API endpoints. ACF stores data in
wp_postmeta.
Pottr gives you a proper schema.
Supabase is great if you're starting fresh. The problem comes when your client needs WordPress — for content, authors, plugins, media. Pottr sits inside the WordPress world, so you get it all without ever leaving.
Nothing. Your data stays exactly where it is — in your WordPress database. Pottr stores everything locally on your client's server. If the connection breaks, the data doesn't go anywhere. Reconnect your app and everything picks up where it left off.
Yes. The free tier stays free, always. You get full access to core features — custom tables, REST endpoints, and basic auth — with no time limits.
Your data is yours. It lives in your WordPress database. Pottr gives you the option to export or clear your data before uninstalling — you're always in control.
No. From their perspective nothing changes — they log into WordPress as normal. The custom app you've built sits on top. They never see Pottr.
That is exactly what Pottr is built for. Single-site, single project — install, define your schema, ship. No over-engineering required.
Get started today
Join the early access list. Limited to 10 spots.
You're on the list. We'll be in touch.
Cancel anytime
14-day free trial on Pro