Camp vs. House
Linkbase is Minute.tech's proprietary platform — and it comes in two versions. Camp is the lightest possible Linkbase site: static-first marketing pages with a working contact form and nothing to log into. House is the full platform — CMS, RBAC, 2FA, e-commerce, compliance tooling, the works. Both are good choices. The question is which one fits the job.
TL;DR. If the site is a brochure — about five pages, a contact form, and nothing to log into — start with Camp. If there's a product catalog, user accounts, content the owner needs to edit themselves, or anything transactional, start with House. Camp sites can graduate to House when they outgrow the brochure.
Pick the right version
- The site is a marketing brochure — home, about, services / features, contact, maybe a couple of supporting pages.
- Content updates are infrequent and a dev can ship them in a PR.
- No user accounts, no shopping cart, no admin to log into.
- Budget and timeline are tight — days to launch, not weeks or months.
- You want the smallest possible surface area to maintain. No database, no auth, fewer dependencies, fewer things that can break.
- Anything sells from the site — physical products, digital products, services, subscriptions, or donations.
- The owner or team needs to edit content themselves through an admin (articles, products, pages, slides, categories).
- Real user accounts are needed — sign-in, dashboards, RBAC, 2FA, or audit logging.
- The business has compliance obligations — encrypted backups, PII deletion, retention policies, SOC 2–shaped tooling.
- The data model isn't just marketing pages — case studies, portfolios, custom content types with structured fields.
What's in each version
| Feature | Camp | House |
|---|---|---|
| Next.js + styled-components foundation | ||
| Static marketing pages | ||
| Contact form (SendGrid) | ||
| Light / dark theme | ||
| SEO, sitemaps, Open Graph | ||
| Database (PostgreSQL + Prisma) | ||
| Admin CMS for non-dev content edits | ||
| User accounts, sign-in, dashboards | ||
| RBAC, 2FA, audit logging | ||
| E-commerce (cart, checkout, Stripe) | ||
| Subscriptions + donations | ||
| B2B checkout (PO, pay-by-invoice, approvals) | ||
| Compliance tooling (backups, PII deletion, audit) | ||
| Client CRM (contacts, notes, billing info) | ||
| REST API + webhooks | ||
| Rate limiting (production-grade, Upstash Redis) |
The graduation path
Camp and House share the same foundation, so projects can move up when they need to. The common pattern: launch on Camp for the brochure phase, then migrate to House when the business adds a product, an account system, or a compliance requirement that Camp can't carry. The brand identity, design system, and content carry across.
Not sure which one fits? Get in touch or take a closer look at the Camp landing site at linkbase.camp.
