Start with production-ready defaults
Ship from a strong baseline instead of assembling core patterns from scratch.
About the project
A foundation for building and launching complete applications
This template is for teams that want a practical open-source starting point for web, API, and mobile products. It combines clear architecture with default tooling so you can ship meaningful features quickly without turning generated code into framework lock-in.
Why it exists
New projects often spend weeks rebuilding the same foundations before solving product problems. This template exists to shorten that cycle: start with sensible defaults, keep boundaries explicit, and stay close to normal application code your team can own.
The goal is not to hide complexity. It is to move repetitive setup work out of the critical path while keeping decisions visible and easy to change.
Keep architecture explicit and understandable
Each app has clear responsibilities, with integration points designed to be obvious.
Automate setup without hiding decisions
Workflows are scripted for speed, but behavior stays inspectable and overridable.
What is included
Vike frontend
SSR/SSG-capable web app with maintainable routing, UI defaults, and testing setup.
Rails API
Backend foundation with auth flows, admin tooling, and operational patterns.
Expo mobile app
Companion mobile client structure aligned to the same API and contracts.
OpenAPI-generated integration
Contract-driven API client generation and shared schema workflow.
Local development tooling
Commands for setup, validation, and day-to-day cross-repo workflows.
Cloud provisioning and validation
Infrastructure scripts and checks for repeatable deployment workflows.
How the applications work together
Vike web app
Expo mobile app
↓
Rails API
Postgres
OpenSearch
Object storage
↓
Workspace orchestration
Principles behind the template
Useful defaults over endless configuration
Automation with visible behavior
Strong boundaries between applications
Generated code that stays maintainable application code
Build from a base your team can grow with
Start with documented defaults, clear architecture, and practical workflows. Adapt the template to your domain while keeping the generated output understandable and maintainable.