CSCornershopdev
An open source website factory

One factory. Every corner shop.

Restaurants, salons, barbers — every trade gets its own brand and its own domain. Behind all of them: one engine, one database, one deploy.

Import, don't onboard A new trade is a config entry Self-host the whole thing

The storefronts

Each trade sells under its own name.

A restaurant should be sold a restaurant product, not a generic website builder. Cornershopdev stays behind the curtain.

RF

Restofront

restofront.com

Live

For restaurants

Menus, bookings and hours that stay current on their own.

Visit Restofront
SF

Salonfront

domain not live yet

In build

For salons and barbers

A service list and a booking button, always up to date.

Visit Salonfront

Your trade next

Dog groomers, dentists, driving schools. A vertical is one directory — catalogue schema, booking providers, prompt, templates and the copy for its own homepage.

See how a vertical is registered

Many fronts. One back.

How a niche ships.

01

A niche gets a domain

restofront.com for restaurants. A nails domain, a barber domain next. Each one is a config entry in the vertical registry and a DNS record — never a new codebase.

02

The factory builds the site

One import pipeline recovers the catalogue, contact details, imagery and existing booking tools, then renders them through that niche's own templates and vocabulary.

03

The owner claims it

Every lead arrives tagged with the niche it came from, into the same database and the same billing. Different storefronts, one operation behind them.

What you actually get

Built to add the next trade cheaply.

The expensive part of a website factory is the second vertical. Cornershopdev is shaped around making that one cheap.

A vertical is a config, not a fork

Schema, providers, prompt, templates and marketing copy live in one directory per niche. Register it and the router, the CSP allow-list and this homepage pick it up.

One database behind every domain

Leads, sites, domains and subscriptions are shared. A niche is a column, so a second trade costs a config entry rather than a second deployment to keep alive.

Import over onboarding

The pipeline starts from what a business already published instead of an empty form. The first thing the owner sees is a finished site, not a setup wizard.

Open source, self-hostable

Next.js, Postgres and durable workflows. Clone it, register your own trade, point a domain at it and run the factory yourself.

Start with the trade, not the tool.

Pick the storefront that sells to your business. The factory behind it is the same either way.

See the niches