Technology & SaaS website templates
Six complete marketing sites for software products, built in Astro 7 and Tailwind 4 — B2B SaaS, a developer tool, an early-stage app, a payments product, an analytics console and a technical instrument. Each is a whole funnel rather than a landing page: a product page, pricing, a deep feature or method page, worked examples, a blog and the legal routes.
Every product shown is invented and the demos are the templates themselves, running. You buy the source through private GitHub access, change the copy, and deploy it anywhere static. One licence covers unlimited sites, your own or a client's. $49 each, or all 62 templates for $199.
- In this set
- 6
- Each
- $49
- Sites per licence
- Unlimited
- Third-party requests
- 0
The 6 builds
Each is loud in exactly one channel — display type, palette, a moving set-piece, texture or the imagery — and deliberately quiet in the other three. That rule is what stops a set like this reading as one layout in different paint. Click any of them to read the build in full and open the live demo.
FENWRIGHT
Deterministic log replay
Loud
Moving set-piece
BELLWETHER
Developer tool / CI test selection
Loud
Display type
MIDSHIFT
Shift scheduling app
Loud
Display type
KELVERN
Payments / money movement
Loud
Moving set-piece
HALVARD
Analytics / operations dashboard
Loud
Moving set-piece
WRACKLINE
Tide prediction app
Loud
Moving set-piece
What software & saas sites have to carry
Every build in this set ships all of it. It is the difference between a template that looks finished and one that is.
- 01 A pricing page, not a pricing section
- Every software visit ends at pricing. All six route it separately with tiers, limits and what is in them, because a pricing anchor buried in the home page is a pricing page nobody can link to.
- 02 One feature or method given its own route
- Timesheets and payroll, how tests get picked, how money moves, how the prediction is made. It is the pattern that grows a software site past its own brand term, and it is the page a technical buyer actually reads.
- 03 Something that answers the procurement question
- Four routed retention policies, a limits page, an integrations page, an accuracy page. These are the URLs you send instead of writing an email during a security review — and almost no SaaS site has them.
- 04 Worked examples, not a demo booking
- Three example rotas, eight tide stations, a changelog. Proof that the product handles the awkward cases, available without a sales call.
- 05 A set-piece that argues honestly
- A replay that genuinely reconstructs state, a partition that keeps all 45 tests, a settlement rail that lands on the real value date. Each one demonstrates the product claim rather than decorating it — and each ships a labelled case where it does not work.
- 06 Written engineering, not marketing filler
- Coverage tells you what ran not what mattered; why the same payment settles on four different days; a chart should morph, not cut. Two or three finished posts per build, each with an opinion in it.
What every build includes
- Astro 7 · static output, no client framework
- Tailwind 4 · one @theme block holds the palette
- Content in typed files under src/data
- MDX blog collection, wired to the sitemap
- Self-hosted woff2 — no Google Fonts request
- Zero third-party requests · strict CSP-ready
- Vitest + Playwright suites in the repository
- Designed 404, sitemap, canonicals, per-route meta
- Private GitHub repo access, with updates
Questions
Do any of these connect to Stripe or a billing provider?
No. Pricing is presented and the CTA points wherever you send it. Billing belongs to your product, and hard-wiring one provider into a template would date it within a year and lock you in.
Which one for a developer-audience product?
The devtool build. It is loud in type by weight rather than scale, ships five colour tokens, carries an install-notes route, and its set-piece makes a technical claim that survives scrutiny. The SaaS platform build is the one for a sale that runs through a security review.
Can I reuse the structure without the set-piece?
Yes, and it is the durable half. Product, pricing, one deep feature page, worked examples, blog is a strong software structure on its own. The set-piece is the part tied to each specific product, and replacing it with your own output is the real work in repurposing one.
Is there a docs site?
No. The devtool build has an install-notes route for marketing-side setup; full documentation normally lives on its own subdomain or in a docs generator, and these link out rather than pretending to be one.
Can I use one template for several client sites?
Yes. The licence is per buyer, not per project — build as many sites as you like, for yourself or for clients. You may not resell the source itself as a template or starter kit.
Other sets
All 62 templates, $199
Every template here plus every future one, delivered as private GitHub repository access with updates. Single templates are $49 each — the 6 on this page alone are $294 bought separately.