PostgREST is a remarkable piece of engineering: a single Haskell binary that turns a PostgreSQL schema into a fast, principled REST API. If you're a Postgres-only team that's already comfortable defining your security model in SQL with RLS, and you don't mind operating the binary and the audit pipeline yourself — use it. It's free.
FastCRUD exists for the cases PostgREST doesn't cover. Your database is SQL Server or Oracle, not Postgres. Your security team wants an audit log they didn't have to wire together from pgaudit, Loki, and a cron job. Your finance team wants a contract, not an infra invoice. We're paid because we replace a stack you'd otherwise build and run for years.
side by side
don't pay us, use them
If any of those describe you, PostgREST is the better fit. We don't want a customer who'll churn the first time their procurement team asks why they're paying $999/mo for what looked like a free binary.
pay us, skip the project
not-postgres support
The most common reason customers move from PostgREST is they acquired (or were always on) a SQL Server or Oracle database and need the same API ergonomics there. We do.
the audit pipeline they kept meaning to build
Setting up pgaudit, shipping logs to S3, defining a retention policy, building an export endpoint — six weeks at every company that does it. FastCRUD ships it.
the access UI
RLS policies are great if you write SQL. They're less great when an internal partner team needs an API key bound to one tenant and your security review wants to see a human-readable scope, not a CREATE POLICY statement.
someone else's pager
If the API tier is on our SLA, it's on our pager. Your team gets to focus on whatever your product actually is.
We'll spin up FastCRUD against a representative slice of your data and walk through the audit log, the access model, and a migration plan from your current PostgREST setup.