If you run an agency, you need a website builder for agencies that eliminates repetitive setup and lets you ship client sites from a single codebase. The Amrify boilerplate is a monorepo template system where every site scores 100/100 on Lighthouse - so you deliver faster, maintain less, and charge more.

Why Agencies Need a Template System in 2026

Every client site you build from scratch costs you margin. You scope the project, set up a new repository, configure the build tooling, install the same plugins you used last time, recreate the same components with slightly different colors, and debug the same responsive issues you have already solved three times this quarter. That repetitive work is not billable, and it is not sustainable.

The maintenance burden compounds. When you have 15 client sites on 8 different stacks, a security patch means 8 different update processes. A design system change means touching every site individually. Quality becomes inconsistent because each site is a snowflake with its own quirks and workarounds.

A proper website builder for agencies eliminates this waste. Shared components live in one place. Bug fixes propagate everywhere. New client sites start from a proven foundation instead of a blank editor. You spend your time on the work that actually differentiates each client - their content, branding, and business logic - not on rebuilding navigation bars and contact forms.

The Amrify boilerplate is built on this principle. One monorepo. Shared layouts, components, and schemas. Per-site configuration for everything that should be unique. Every site ships with a 100/100 Lighthouse score because the performance work is done once and shared across every project.

What You Get with Amrify

The boilerplate is a complete website builder for agencies, architected as a pnpm monorepo with Turborepo for parallel builds and intelligent caching.

Shared packages contain your layouts, components, utility functions, and Zod schemas. Update a component once, rebuild, and every client site picks up the change. No copy-pasting between repositories, no version drift between projects.

Per-site configuration keeps each client unique. Every site has its own config.json for business details, theme.json for colors and typography, and content directories for pages, blog posts, services, and FAQs. Swap out a client’s entire color palette by changing six CSS custom properties in a single file.

Content collections with typed Zod schemas mean your content editors get clear validation errors instead of broken builds. Each site can define its own content types or use the shared defaults - blog, services, about, contact, FAQ, pricing, and legal pages are all pre-built and ready to populate.

Turborepo handles the build orchestration. Build a single client site in seconds with caching, or build the entire portfolio in parallel. Only the sites that changed get rebuilt. Deployments are fast even as your portfolio grows to dozens of sites.

Amrify ($249 founding price for the first 5,000 members, then $399) gives you a complete agency site ready to deploy with blog, case studies, and structured data - plus the monorepo system, white-label capabilities, every other niche template, and unlimited client sites. Pay once, own it forever - no monthly subscriptions.

Built for Scale

Scaling an agency means adding client sites without proportionally adding overhead. Amrify’s architecture is designed for exactly this growth pattern.

Adding a new client site takes minutes, not days. Duplicate an existing site directory, update the config files with the new client’s business details and branding, add their content, and deploy. The shared components, build pipeline, and SEO configuration are already in place. You are not setting up a new project - you are configuring an existing system.

Deploy each site independently to any static hosting provider. Vercel, Netlify, Cloudflare Pages, and AWS all work out of the box. Each client site can live on its own domain with its own deployment pipeline, or you can deploy the entire portfolio from a single CI/CD workflow. There is no shared runtime, no multi-tenant server, and no single point of failure.

Quality stays consistent because every site shares the same battle-tested components and build process. When you fix a bug in the shared navigation component, every client site gets the fix on the next build. When you add a new feature to the shared FAQ component, every site can opt into it without custom development.

The performance guarantee is real and measurable. Every site built with Amrify scores 100/100 on Google Lighthouse because the architecture makes it nearly impossible to ship a slow page. Static HTML, zero client-side JavaScript by default, optimized images, and proper cache headers are baked into the build process. You can show every client their Lighthouse report and know it will be perfect.

Frequently Asked Questions

How many client sites can I run?

There is no artificial limit. The boilerplate covers unlimited client sites from a single monorepo. In practice, we have seen agencies running 20+ sites from one repository with no issues. Turborepo’s caching ensures build times stay fast regardless of portfolio size.

Do client sites share a hosting plan?

No. Each client site is an independent static build that deploys separately. You can host different clients on different providers if you want. Most agencies use a single provider with separate projects per client for simplicity, but the architecture does not enforce any particular hosting structure.

Can I white-label the templates?

Yes. There is no Amrify branding anywhere in the client-facing output. The generated HTML, CSS, and JavaScript contain no references to Amrify. Each site uses the client’s brand name, colors, fonts, and content exclusively. Your clients see their brand, not yours.

How do I onboard a new client site?

Duplicate an existing site directory in the monorepo, update config.json with the client’s business name and details, adjust theme.json with their brand colors and typography, replace the content files with their copy, and deploy. The entire process takes less than an hour for a basic site. Most agencies create a documented onboarding checklist that a junior developer can follow without senior oversight.

---

See live examples on our Showcase page.

Compare with alternatives: Amrify vs WordPress | vs Wix

Ready to scale your agency? Get the boilerplate above or contact us to discuss your setup. Looking for a different industry? Check out our small business templates for single-site clients, freelancer templates for independent developers, SaaS templates for software product sites, or nonprofit templates for mission-driven organizations. Agencies running content-heavy client sites should explore the ecommerce templates and portfolio templates as well.