$fastcrud
~ fastcrud vs hasura

Hasura is a great tool. It just isn't the right tool for legacy enterprise databases.

Hasura GraphQL Engine is excellent when you're building on a fresh PostgreSQL instance, want subscriptions, and have a team that's comfortable modeling permissions in their DSL. If that's you, use it.

FastCRUD is for the other case — the team running a 20-year-old SQL Server or Oracle database, where the schema can't be rewritten, security review is brutal, and the audit log is a hard requirement, not a nice-to-have. We treat SQL Server and Oracle as first-class peers to Postgres, and we ship the audit log on every plan instead of behind an Enterprise SKU.

side by side

#how the two compare on the things that actually decide procurement

No green-check tables. Where Hasura wins, it says so. Where the distinction is a tie or depends on context, it says that too.

feature
FastCRUD
Hasura
●Primary database focus
SQL Server, Oracle, PostgreSQL, MySQL, MongoDB — treated as peers.
PostgreSQL-first. Other databases via paid Cloud connectors with reduced feature coverage.
●Audit log
Built-in on every plan. Actor, IP, query, latency, outcome — exportable.
Available in Enterprise tier or via external services (Datadog, custom). Not the default.
●Permission DSL
Per-key scopes + row-level filter strings (column.operator.value). Click-to-configure in the dashboard.
Hasura permission engine — powerful, but requires learning a DSL and modeling permissions per role/table.
●GraphQL subscriptions
Not yet — queries and mutations only.
First-class WebSocket subscriptions.
●Stored procedure exposure
Discovered at introspection time, exposed as typed REST or GraphQL endpoints with arg validation.
Hasura Actions wrap arbitrary HTTP endpoints — you build the proc wrapper yourself.
●Hosting model
SaaS by default. BYO-VPC and on-prem on Enterprise.
SaaS (Hasura Cloud), self-hosted CE, or self-hosted EE.
●Procurement
B2B SaaS — invoice billing, custom MSA, DPA, BAA. No usage-based surprise bills.
Per-request and per-seat pricing on Cloud, EE licensing for self-host.
●Maturity
Newer. Smaller community. SOC 2 in progress.
Mature, large community, broad ecosystem.
● FastCRUD edge● Hasura edge● equivalent

when not to pick fastcrud

#reasons to choose Hasura instead

We'd rather lose a deal where the fit isn't there than oversell you and churn six months later. If any of those bullets describe you, go with Hasura.

when to pick fastcrud

#why our customers switched

the database

Their production data lived in SQL Server or Oracle and the Postgres-first answer was always "migrate first." FastCRUD plugs into the database they already have, with first-class introspection of stored procedures, computed columns, and composite keys.

the audit log

They needed exportable audit trails for SOC 2 or HIPAA on day one, not after upgrading to Enterprise. FastCRUD ships them on Free Trial and up — every plan, every endpoint.

the procurement model

Their finance team wanted a fixed annual line item with a real contract — not a metered bill that swings with traffic. FastCRUD Business and Enterprise bill on invoice with a flat tier and predictable overage.

the permission model

They didn't want to maintain a permission DSL across every table. Per-access-key row filters and column scopes were fast to configure and easy to audit.

$ see it on your schema.

20-minute demo against either a representative schema or yours (under NDA). We'll show the audit log, the per-key access model, and how the SQL Server / Oracle introspection actually handles your stored procedures.