Your site is yours. Here is what happens after launch.
When we build a site, we do not hold it captive because we know something you do not. The code, the design and the content are yours. What happens next is your choice, and every option is a real one.
Here are your real 3 options
Take it and run it yourself
You take the code and host it wherever you like. We use Railway; Vercel, Cloudflare or AWS work just as well. Choosing this means the site is entirely yours and we step back: from that point we are not responsible for its uptime, security or updates. You can come back any time. You will need:
- A hosting service that runs Next.js
- An email service, such as Postmark, so the forms can send
- A Cloudflare account, for Turnstile form protection and R2 image storage
- Your images: they live in our R2 account today and we hand over every file
- A GitHub account to receive the repository
Hand it to another developer
Everything in the handover above goes to them instead of you. Nothing in the build is proprietary or hidden, and the repository documents how it is put together, so any developer who knows Next.js can pick it up.
Host it with us on Evergreen
We run it, keep it current and stand behind it, on one monthly price with no setup fee and no minimum term. Hosting, DNS and email run under our accounts because operating them is the service. The code stays yours, in a repository you can see from day one, and leaving later is option one or two, whenever you like. Here is how that works.
Three ways we can run it
Every tier is for one site we built. Most sites are on Plus.
Core
We run it.
- Hosting and operations, fully managed
- Quarterly update cycle through the full gate set
- Uptime monitoring with alerts to us
- Security headers, firewall and bot protection maintained
- Changes quoted per request, as a flat price
Plus
We keep it current.
Everything in Core +
- We apply the content you send: a new service, a location page, a blog post, a price change. You write it, we adapt it for the site and ship it
- A monthly report: the site scan, traffic from your analytics, and search positions and clicks from Search Console
Studio
We grow it.
Everything in Plus +
- One search-ready piece every month: researched against what the site already ranks for, written in your voice, built, linked from the pages that should point to it and shipped through the gates
- A quarterly review call: what changed, what to improve next
- Performance and accessibility re-audits after every update cycle
What every tier includes
- Hosted and operated for you. Your site runs on Railway behind Cloudflare, with the web application firewall in front of it and Turnstile bot protection on every form. Images are served from Cloudflare R2 and email goes out through Postmark. You never touch a server or a dashboard.
- Recoverable by design. Every change ships as a git-versioned deploy. Any earlier version can be put back in minutes, so there is no backup schedule to trust and nothing to restore by hand.
- Kept current, every quarter. The current framework, dependency and security releases come in, and each one passes the build, type check, Lighthouse and axe gates before it goes live.
- Accessible and checked on every update. WCAG 2.2 AA with axe at zero violations, on desktop and on mobile. This lowers your risk of complaints; no site can be made immune, and this is not legal advice.
- Private and pleasant. Analytics and forms stay set up to meet GDPR and CCPA, without a consent wall that gets in your visitors' way.
- Watched. Uptime monitoring checks the site around the clock and alerts us, not you, if anything stops answering.
Updates are improvements, not a requirement
Your site does not need updates to keep working. Unlike a WordPress site, nothing expires and nothing breaks if it is left alone. What the quarterly cycle does is make it newer: the current framework comes in, security fixes land and the site gets a little faster and a little better each time, with every change checked before it goes live.
What counts as a change
If you bring the content, it is a change. If it changes what the site does, it is a project. Text, prices, images, a new service or location page from your copy, a blog post you wrote: those are changes, and on Plus and Studio we apply them. New integrations such as booking or a CRM, design changes and changes to how a form behaves are projects, quoted separately. Pages we research and write for you are Studio. Content is applied as long as it is the kind listed here and arrives at a reasonable pace. If a request is really a project, we say so up front and quote it before touching anything.
Questions people ask
What does it cost?
Evergreen is priced per site on a short sheet we send on request, so you see the tiers, the prices and what each one includes in one place. Builds are quoted per project.
What happens if I cancel?
Tell us 30 days ahead. We transfer the repository to your GitHub account, help you point your domain wherever it goes next and you redeploy on any host that runs Node. There is nothing to migrate out of and nothing to buy back.
Can I start on Evergreen later?
Yes. If we built the site, you can move it onto Evergreen at any point, including after running it yourself for a while.
Is Evergreen available for a site someone else built?
No. The update cycle and the gates depend on how the site is built, so Evergreen is for sites we built. If you have a site that needs care, start with the free site check and we will tell you plainly whether a rebuild makes sense.
The build details behind every promise on this page are public.
Ask for the Evergreen sheet
One email. We send the tiers, the prices and what each one includes, and you decide with the whole picture in front of you.
Ask for the Evergreen sheet