ShipRust vs Gerust: SaaS app or API foundation?

Choose Gerust for an API-first Rust backend with structured scaffolding. Choose ShipRust for a server-rendered SaaS starting point with account pages and optional billing. Both use Axum and SQLx, so choosing between them is mostly about what you want the generated application to do.

We build ShipRust. This comparison is based on our source and Gerust's public documentation, checked October 12, 2026. We have not run comparative benchmarks.

Start with the application boundary

Gerust is Mainmatter's Rust backend project generator. Its architecture guide explicitly targets API servers, rather than websites rendering HTML and handling browser forms directly. That is a useful design boundary, not a deficiency.

ShipRust generates an application with Maud-rendered pages, plain CSS, email/password accounts, and a dashboard. You can include an authenticated API too, but the browser interface is part of the starting point.

Your intended product	Start your evaluation with
Backend for a separately built frontend	Gerust
JSON service without a customer-facing website	Gerust
SaaS with account forms and a server-rendered dashboard	ShipRust
SaaS with an API alongside the browser application	ShipRust, then assess your API requirements

This is a fit guide, not a statement that either tool prevents another architecture.

Three reasons to choose Gerust

• You want an MIT-licensed generator you can inspect before committing to a paid starter.
• Your frontend is already chosen, and you primarily need a Rust API foundation.
• You want CLI scaffolding for controllers, middleware, entities, and tests.

Gerust documents a Cargo workspace that separates web, configuration, command-line tooling, and database concerns. Its minimal-project tutorial also shows a database-free starting point with a generated endpoint, tests, and GitHub Actions checks. You need not start with a full SaaS to use it.

What changes when you choose ShipRust

The reusable work in ShipRust is closer to the customer journey: verified signup and sessions, signed-in pages, and optional Stripe billing. Its generation options include API and MCP endpoints, file storage, blog/docs pages, and provider integrations.

The purchase buys that starting point. It does not buy your product's domain model. You still define ownership rules, decide which actions require payment, and configure external providers. The billing starter has one recurring price and one optional one-time price; multiple tiers require an extension.

A practical way to compare: draw the path from your homepage to a customer's first useful action. Mark which screens your separate frontend already supplies. If nearly all of them exist, Gerust may be the more focused backend choice. If you need to build the account and dashboard flow too, read ShipRust's download guide before making the decision.

Price and next step

ShipRust costs $999 once for lifetime access to unlimited projects, documented in getting started on October 12, 2026. Hosting and provider charges are separate, and generated signup needs your Mailgun configuration.

You should pay for a starting point that matches your product, not for the longest feature list. If you want ShipRust's server-rendered approach, create an account, verify your email, purchase access, and generate your project.