Validation landing pages for technical founders. Capture signal before you build.

• Landing pages with email capture, presales, and booking flows
• Authority docs with citations, cross-linking, and MCP integration
• Event tracking that streams to your webhooks (Telegram, Slack, Discord)
• Zero lock-in — standard Nuxt app, swap any tool anytime

Stack: Nuxt 4 · Tailwind v4 · TypeScript

npx create-foundry my-project
cd my-project
npm install
npm run dev

Or install the layer directly:

npm install @incubrain/foundry

// nuxt.config.ts
export default defineNuxtConfig({
  extends: ['@incubrain/foundry']
})

Email Capture — Test interest before creating content Presales — Collect payment before building (external links to Stripe/LemonSqueezy) Service Bookings — Sell calls via Cal.com/Calendly, learn from delivery

layer/              Nuxt layer (npm: @incubrain/foundry)
examples/
  ├── foundry/      Demo site
  ├── astronera/    Real-world example
  └── starter/      Minimal template
cli/                create-foundry CLI

Edit content files, not code:

content/
├── config/         Site config (YAML)
├── pages/          Landing pages (Markdown)
└── faq/            FAQ entries (YAML)

Set up webhooks:

cp .env.example .env
NUXT_WEBHOOK_URL=https://discord.com/api/webhooks/...

• Email sequences (use ConvertKit/Mailchimp)
• Authentication (validation ≠ product)
• Payment processing (external links only)
• Databases (webhooks stream to your destination)

These belong in your product, not your validation tool.

• Documentation
• GitHub Issues
• Discussions

MIT