A Salty Vet · Field Reference · Cleared for public release
Project file2026
Problem
Most website builders hold your code hostage. Foundry Kit produces portable source a user can leave with — the offer is the exit.
Role
Founder, product strategist, systems designer, frontend engineer
Date
2026
Tools
Next.js, React, Auth, Postgres, AI SDK, Cloudflare, Stripe-ready architecture
Website BuilderSaaSSource ExportCloudflareProduct
W
Work detail

Foundry Kit

LivePublicVerified

A website builder with the exit built in: plain-English brief in, exportable source code out. Pricing, docs, templates, security posture, and status — all published.

Claim: a site builder that doesn't trap its users.

Receipt: a live product at foundry-kit.com with builder, pricing, docs, templates, security, and status surfaces. The offer is narrow on purpose: describe a site, revise it, export ordinary source files, host them anywhere static files run.

Mission now: instrumentation. Wire payments, web analytics, and one narrow paid-offer path — so "will it sell?" gets answered with data instead of hope.

Status honesty: live product, unproven funnel. As of this writing there is no instrumented revenue path — which is exactly what the current mission exists to fix. Trust surfaces shipped before marketing; revenue proof comes next or the register says why not.

Artifacts

Screenshots and visual proof.

ArtifactScreenshot
Foundry Kit public homepage showing the website builder product surface.
Live public website-builder product surface.

Receipts

Outcomes and lessons.

Outcomes

  • Live public site with builder, pricing, docs, security, status, and example surfaces.
  • Public copy centers on portable source export and static hosting readiness.
  • Private implementation details stay summarized, not exposed.

Lessons

  • The honest offer is narrow: generate a useful site, leave with the code.
  • No platform adapters get built before the core export promise is proven.

Foundry Kit is the founder-lane proof: positioning, trust surfaces, export logic, security posture, pricing model, and deployment thinking in one product — shipped, then instrumented, in that order because the first part is done and the second is in progress.

What stays private: provider costs, internal prompts, user records, and unfinished adapters. They appear here only if they're intentionally cleared later.