Production TypeScript template

Build the SaaS, not the stack archaeology.

rentwifi.now is a production-ready TypeScript monorepo for teams who want Cloudflare Workers, TanStack Start, Hono RPC, Better Auth, D1, jobs, docs, and admin foundations already connected.

Open the app shellRead the docs

Included foundations

The pieces teams usually stitch together after the deadline slips.

rentwifi.now keeps the template opinionated without hiding the underlying stack. Each capability maps to a package, app, or documented pattern you can inspect and replace.

Edge API foundation

Hono on Cloudflare Workers with typed routes, Zod boundaries, and production CORS defaults already wired.

Typed app surface

TanStack Start, Router, Query, and Hono RPC patterns line up so frontend calls stay type-aware end to end.

Auth that survives deploys

Better Auth setup accounts for split domains, SSR session guards, cookie forwarding, and redirect base URLs.

D1 data layer

Drizzle schema, migrations, seeding, and D1 constraints are documented where teams usually lose time.

Async jobs package

Trigger.dev lives in the monorepo from day one for background work, retries, and long-running product flows.

Multi-app starter kit

Website, app, API, backoffice, shared UI, database, auth, jobs, common utilities, and mobile foundation ship together.

Production problems solved

A starter that remembers the deployment bugs.

The template is positioned around real full-stack friction: auth redirects, edge deployment, environment detection, database constraints, and route-level data boundaries.

Less boilerplate theatre. More shippable defaults.

rentwifi.now does not pretend every app is the same. It gives you a reliable baseline for the parts most products share, then documents where to customize it.

Environment drift

API URLs, Worker bindings, domains, and local ports are treated as template variables instead of tribal knowledge.

Auth edge cases

The template documents the redirect, cookie, CORS, and SSR session pitfalls that typically appear after launch.

Cloudflare data realities

D1 limitations such as transaction behavior and integrity assumptions are reflected in the architecture guidance.

Unclear starting points

Docs, examples, repo rules, and package boundaries make it obvious where product code should live next.

Architecture snapshot

One repo, clear seams, no mystery runtime.

The website stays static and docs-first, while product surfaces share the same UI, auth, data, and deployment assumptions across the monorepo.

Experience

  • Marketing website
  • TanStack Start webapp
  • Refine backoffice
  • Expo mobile foundation

Application

  • Hono Worker API
  • Hono RPC client
  • React Query state
  • Shared UI package

Platform

  • Cloudflare Workers
  • D1 + Drizzle
  • Better Auth
  • Trigger.dev jobs

Operations

  • Turborepo tasks
  • Dev container
  • Template initializer
  • Production fix notes

Quick start flow

From template to product workspace in three deliberate moves.

The fastest path is not a blank repo. It is a documented sequence that preserves the production assumptions already encoded in rentwifi.now.

01

Initialize the template

Rename the product, set domains and ports, and generate the environment scaffolding with the project initializer.

pnpm run init-project
02

Install and run locally

Bring up the workspace with pnpm and keep API, app, docs, database studio, backoffice, and native defaults aligned.

pnpm install && pnpm dev
03

Build on the slices

Start from the documented API, auth, data, UI, job, and route patterns instead of assembling them from scratch.

open notes/PRODUCTION_FIXES.md

Docs and resources

The landing page points into the system, not away from it.

rentwifi.now is most useful when the homepage acts as a gateway to architecture notes, stack decisions, and implementation guidance.

Template reference

Map every replaceable app name, domain, port, and package convention before you ship a fork.

Open docs

Production fixes

Study the deployment and auth pitfalls absorbed into the template so your app starts past the usual blockers.

Review fixes

Implementation notes

Use the blog and docs bridge for ongoing decisions around stack choices, constraints, and template evolution.

Read notes
Questions before adopting it?

Talk through your rentwifi.now starting point.

Use the existing contact form if you want to discuss whether the template fits your deployment model, team workflow, or SaaS roadmap.