Rails + Vike Template

Build production-ready applications faster.

A clean full-stack starter designed for real teams: frontend with Vike + React, backend-ready API integration, pragmatic defaults, and deployment-oriented structure.

Northline Dashboardlocalhost:3000

Active users

12,480

+8.2% this week

API health

99.96%

p95 latency 182ms

Deployment status

API: healthyWeb: healthySearch: healthy
Open Source
MIT Licensed
Fast
Type Safe
Production Ready

Features for real product work

A reusable baseline for SaaS, AI, and business applications that balances clarity, speed, and maintainability.

Fast Development

Hot reload, practical structure, and route patterns designed for iterative delivery.

Authentication

Sign-in and sign-up flows wired for token-auth based Rails APIs.

Analytics Ready

Clear layout for metrics screens and observability-driven feature work.

Cloud Deployments

Deployment-friendly defaults with infra workflows for production setup.

AI Friendly

Simple architecture and conventions that AI coding agents can reliably extend.

Mobile Alignment

API and UI patterns that map cleanly to companion mobile clients.

Architecture overview

Designed for a clear data path between frontend and backend systems.

Frontend (Vike + React)
↓
Rails API
↓
Postgres
↓
OpenSearch

Product screenshots

Use real product views to explain what users can do on day one.

┌───────────────────────────────────────────────┐
│ Revenue     $248,900        +12.4%            │
│ Active Users 12,480         +8.2%             │
│ Conversion   5.7%           +0.6%             │
├───────────────────────────────────────────────┤
│ Latest Deploy: main  •  3m ago  •  healthy    │
└───────────────────────────────────────────────┘

Getting started in three steps

A visual baseline to keep onboarding straightforward.

1. Clone

Copy the template and initialize your workspace.

2. Configure

Set environment values, auth, and service endpoints.

3. Deploy

Run validation and ship with CI and production defaults.

Frequently asked questions

Defaults you can keep, customize, or replace as your product evolves.

Can I use this for non-SaaS apps?
Yes. The page and component structure is intentionally generic and suitable for most product types.
Do I need Rails to use the frontend?
No. Rails integration is provided by default, but the app can target any compatible API.
Is this production-friendly?
Yes. It includes lint/test/build scripts, SEO defaults, and deployment-ready structure.
Can we simplify the landing page further?
Yes. Remove sections you do not need while preserving the spacing rhythm and typography scale.
Is the local CMS intended for production serving?
No. Local CMS tooling is for authoring workflows; production serves the built web output.

Ready to build?

Start with a clean, modern baseline and adapt it to your product without redesigning from scratch.