rSQL is a developer-focused data access tool. Its website positions it as “Goodbye API. Hello rSQL,” aiming to reduce the work of building REST or GraphQL APIs by allowing clients to access data directly through secure, versionable, and extensible SQL. Its core value is shifting part of the traditional API layer’s responsibilities into SQL query parsing, access control, and version management.
Based on the captured text, rSQL focuses on fine-grained authorization, version control, authentication, and rate limiting. It parses incoming SQL queries and uses ACLs to determine which data can be returned or updated. It also claims to help teams handle schema versioning so that data structure changes do not break the frontend. For authentication, it mentions JWT and third-party OAuth integrations; for database protection, it mentions rate limiting. However, the page does not specify which databases, languages, frameworks, or client SDKs are supported, nor does it provide sample queries, deployment architecture, or auditing capabilities.
The page lists a free Basic plan, Standard at $29/month/seat, Premium at $49/month/seat, and an Enterprise plan. However, the same section clearly includes content from the Landkit theme template, so it is not possible to confirm whether this is rSQL’s real pricing. Documentation, Changelog, About, and Blog are marked as Coming soon in multiple places, and the so-called documentation in the latter half of the page is Landkit template documentation rather than rSQL documentation. For a developer tool, this significantly affects evaluation and onboarding.
The main advantage is a clear product direction: it may suit teams that want to reduce repetitive CRUD API work while still needing ACLs, JWT/OAuth, rate limiting, and version control. The downside is limited disclosure: it is unclear whether the product is open source or closed source, whether it supports self-hosting, which databases are compatible, what SDKs exist, and whether there are production case studies. The “direct SQL access” model also places high demands on permission boundaries, query restrictions, and auditing; without proper documentation, the risk is even higher.
It is better suited to early-stage teams willing to experiment with API-alternative architectures, or to internal tooling scenarios. It is not suitable for direct adoption in production systems that require strong compliance, stability, and long-term support. Access from China cannot be determined from the captured text; the only payment method visible is a card form. Mature alternatives to compare include PostgREST, Hasura, Supabase, Prisma, and Directus.
⚠ This review is compiled from public sources and does not constitute a purchase recommendation. Verify all facts on the vendor's official site. Verify on rsql.io official site.
rsql.io is an Unknown Dev Tools provider. TG4G tracks its product information, an overall rating of 5.0/10, and a China-accessibility score of Workable. Click "Visit Official Site" to reach rsql.io directly.