The kit gallery · 45 kits · 8 shelves

Every kit is a product foundation, not a homepage.

An Eastbase kit is a launch-ready Next.js codebase: the landing page plus the app screens, auth and legal pages, designed states, sample data, and guides it takes to actually ship. Each one is built for a specific niche — and documented so you, or the AI agent working with you, can make it yours without reverse-engineering anything.

Every screen previewable before you decide · no email wall

The top shelf

Start with the 4 we'd show first.

Featured is earned, not promoted — the catalog's strongest work, one per shelf, rotated as the bar rises.

The full catalog

Every public kit, on one shelf.

Filter by what you're building, or search by niche. Every card opens a live preview — screens, states, and all — so you can count what's included before you decide.

Prices shown are placeholder — checkout isn't live yet, so nothing is charged today.

11 of 45 kits

How to choose

Start from what you're launching.

No two kits do the same job. Where two look like neighbors, they're built for different work — here's the honest difference.

An AI or B2B SaaS

  • SignalDeskthe sharp, dark flagship look
  • Leveea cost console that reads like an instrument
  • Soundinga public feedback board and roadmap

A developer tool or OSS project

  • DevLaunchthe dark dev-tool landing
  • OpenForgeturns GitHub stars into contributors
  • Formfeedlanding plus real API-console screens

A tool your team runs the day on

  • Halfhourbookings without the back-and-forth
  • Groundcrewthe ops board with an audit trail
  • Wellmetthe book of business, kept warm

Client work, sold by you

  • FounderPagethe one-pager that books calls
  • Soloistruns the practice, proposal to paid
  • AtlasAgencythe studio site that lets casework speak

A visual portfolio

A show, newsletter, or course

Things you make and sell

A community or event

Tables, stays, or appointments

Inside every kit

One packing list, 9 lines, no exceptions.

Every kit in the gallery clears the same written quality bar before it's listed. This is the box, line by line:

01

Landing page

Conversion-led and written for the niche, not lorem ipsum.

02

App screens

2–3 niche product screens designed for the kit — not stock dashboards.

03

Auth pages

Themed sign in / sign up patterns, ready to wire to your auth.

04

Legal & trust

Terms and Privacy starter pages, typeset like the rest of the site.

05

Designed states

404, 500, loading, and empty states that carry the kit's theme.

06

Sample data

A coherent fictional brand with numbers that add up.

07

Guides

Customization, deployment, and troubleshooting, written for buyers.

08

Launch checklist

The practical, step-by-step path from download to live.

09

Agent docs

AGENTS.md + DESIGN.md, so an AI agent can extend it safely.

Responsive throughout, with lightweight CSS-first animation that honors reduced motion. Not included — and said plainly: a backend, CMS, or wired-up auth. Kits are foundations; WIRE: markers show exactly where your product plugs in.

Built for AI agents

Your agent reads the docs, not tea leaves.

Every kit is config-driven — copy, links, pricing, and theme are data, so customizing is an edit, not component surgery. The docs in the box tell an agent (Claude, Cursor, or whatever's next) what it may touch and how, and every kit page has a “Copy as AI context” button with a ready-made starter prompt. The studio even serves an /llms.txt so agents can read the whole catalog.

Honestly: an agent follows the docs, it doesn't do magic. You still review the output — the docs just make that review short.

what ships in every kit
  • AGENTS.mdOperating rules, a project map, and starter prompts for the kit.
  • DESIGN.mdThe design system and theming contract — tokens, not hard-coded colors.
  • configThe safe editing zone: copy, links, pricing, and theme are data, not component code — AGENTS.md names the exact files.
  • docsCustomize, deploy, launch checklist, troubleshooting — for humans too.

The fine print, promoted

Who's behind this, and what you actually get.

Operated by

Eastbase Kits is a product line of Eastbase Studio. A real inbox answers: support@eastbase.studio

What you receive

Full Next.js source, guides, and checklist — one-time payment, single-project license. See the license and refund policy.

What needs a human

Legal pages are structured starters — have a professional review them. Your claims, your pricing, and your product's wiring are yours to own.

Before you buy

The questions buyers ask us.

How is this different from a normal template?

A template is a homepage. A kit is the homepage plus the product around it: 2–3 niche app screens, sign in / sign up, Terms and Privacy starters, designed 404/500/loading states, coherent sample data, buyer guides, a launch checklist, and agent docs. Open any preview and count the screens — that's the difference.

Do I need to be a developer?

You need to follow a guide: install Node, edit config files, deploy. Each kit states its difficulty and setup time honestly on its page, and the setup service exists if you'd rather not touch any of it.

Can I customize a kit with an AI agent?

That's the intended path. Every kit ships AGENTS.md and DESIGN.md, keeps content as editable data — not component code — in the files AGENTS.md maps, and its kit page has a Copy-as-AI-context button with a starter prompt. Agents follow the docs — you still review what they produce.

What pages and screens are included?

Every kit: a landing page, sign in / sign up, Terms and Privacy, 2–3 app or product screens designed for its niche, and themed 404/500/loading states. The exact list is on each kit's page, and the live preview lets you click through all of them.

Are the legal pages ready to use?

They're structured, typeset starter pages with example content — a real head start, not legal advice. Have a professional review them before you rely on them.

Do kits include a backend, auth, or billing?

No — deliberately. Kits are front-end foundations: the auth screens are finished UI ready to wire to your provider, and WIRE: markers show where a backend plugs in. Nothing pretends to work until you wire it.

Can I use a kit for client work?

Yes — the single-project license covers one live project per purchase, your own or a client's. Building another site with the same kit means buying it again. Details on the license page.

What happens after purchase?

Where checkout is open you get an instant, license-gated download, and the kit lives in your account for re-download. Kits marked “coming soon” aren't buyable yet — request early access from the kit page and we'll email you when they are.

How do I get support?

Every kit bundles troubleshooting notes, and support@eastbase.studio is a real inbox. For hands-on help, request the setup service and we'll get it live together.

Still deciding? The two free kits are complete, downloadable, and the fastest way to judge the quality bar.

Inspect a free kit