ShipRust vs Rust SaaS Boilerplate: source checked

ShipRust and HardikKSavaliya's Rust SaaS Boilerplate are at different starting points. ShipRust generates an application with verified signup, sessions, and optional Stripe billing. The open-source repository provides an Axum/SeaORM scaffold, but its current source does not match all the authentication and billing features advertised in its README.

We build ShipRust. We inspected the repository at commit 5a0575d on October 12, 2026. This is a source review, not a runtime test or a claim about every project called “Rust SaaS Boilerplate.”

What the source actually includes

The repository README lists JWT authentication, Argon2 password hashing, and optional Stripe subscriptions. Those claims need checking against the implementation.

At the reviewed revision, the application router wires health and user CRUD routes. The user-creation handler still marks password hashing as work to implement. Treat it as application scaffolding, not a finished authentication flow.

The roadmap lists authentication and Stripe billing as unfinished. Some database items are also unchecked even though database code exists, so the roadmap alone is not a reliable feature inventory either.

Area	ShipRust	Reviewed repository
Database access	SQLx with PostgreSQL	SeaORM with PostgreSQL
Accounts	Verified signup and server-side sessions	User CRUD; authentication work remains
Billing	Optional Stripe integration	Listed on the roadmap
Starting experience	Generated app with browser pages	Backend scaffold to extend

Three reasons to choose the repository

• You want an MIT-licensed starting point with no starter purchase.
• You prefer a SeaORM-backed example to ShipRust's SQLx approach.
• Your goal is learning or implementing the account and billing layers yourself.

Those are reasonable reasons to fork a scaffold. They are different from expecting a ready-to-configure customer signup flow. Review the current revision before using it: this comparison may become outdated as the project changes.

What ShipRust provides instead

Our authentication walkthrough describes the implementation behind email verification, Argon2id hashing, and Postgres-backed sessions. The generated app includes sign-up, sign-in, and dashboard pages rather than leaving their connection as an exercise.

Optional Stripe billing supplies Checkout, a customer portal, and webhook handling. It supports one recurring price and one optional one-time price. You still add product-specific paid-feature gates; choosing a starter does not finish your permissions model.

Our suggested buying test is concrete: trace registration through verification, sign-in, and one protected action. Then trace a payment through its webhook to an access decision. Inspect the code and tests behind both paths instead of counting README checkmarks.

Decide how much foundation you want to build

ShipRust costs $999 once for lifetime access to unlimited projects, as documented in getting started on October 12, 2026. Hosting and provider fees are extra; configure email before using generated signup.

If you want to begin with the connected application, create and verify your account, purchase access, and generate a project. If building the missing foundation is part of the exercise, the open-source scaffold may be the better fit.