gr8s serves your exported SPA or static site from a single lean Go binary, then analyses each page for meta tags, headings, links and schema while it renders. Let us host and deploy it for you, or run the same single container on your own server. No server components, no hydration errors, no separate SEO audit toolchain.
Every page is scored for title, description, heading order, image alt text, schema readiness, internal links and content quality as part of rendering. The feedback arrives while you build, not weeks later from an external crawler.
Peer-reviewed benchmarks measured gr8s serving the same workload with about 5x fewer servers, roughly 9.8x lower overall energy use, and 82.54 MB of memory against 411.91 MB for Next.js.
Build your app on the client, export it, and let gr8s render it. There are no server components, no client/server boundary directives, and no hydration mismatches to debug at 2am.
Turn it on and gr8s re-crawls the site on a schedule and fills in missing titles, descriptions, canonicals and Open Graph tags automatically, while leaving pages you edited by hand untouched. Pro and Scale.
Pro and Scale sites get a real-time analytics dashboard from self-hosted Plausible, embedded in the control panel. Free sites get lightweight, anonymised page counts. Cookieless and GDPR-friendly, with no consent banner and no third-party tag to trust.
Every site ships a sitemap.xml and robots.txt, and Pro sites notify IndexNow (Bing, Yandex, Seznam, Naver) whenever pages change, so new URLs are re-crawled quickly instead of waiting for a periodic sweep. The pipeline can also emit an llm.txt, a clean plain-text summary that AI assistants and answer engines read directly.
Most teams reach for Vercel and Next.js, or keep a static host and bolt SEO on afterwards with a separate crawler. Here is how gr8s compares with each, and with doing nothing.
Export your frontend the way you already do. gr8s does not change how you build.
From the dashboard (free): pick your build folder and deploy, nothing to install. From CI (Pro): set your domain and API key and run one command. The deploy transforms index.html for the server and pushes the whole build.
Prepare the build once with gr8s-cli, then serve it with the single gr8s container on your own machine.
# --- managed from CI (Pro): transform and deploy in one command --- pnpm install -g @codomatech/gr8s-tools export GR8S_DOMAIN=www.example.com export GR8S_API_KEY=xxxxxxxxxxxxxxxx gr8s-cli --deploy -f dist/index.html # the dashboard does the same with no CLI: pick your build folder, deploy # --- self-hosted: prepare the build, then run it yourself --- gr8s-cli -f dist/index.html docker run codomatech/gr8s
An honest look at where gr8s wins, where Next.js and Vercel win, and how to decide. The point is not that one is universally better, it is that the trade-offs differ by team.
The efficiency results were peer-reviewed and published at IT IS 2023. They cover server count, energy use, memory and the projected carbon saving if Next.js SSR sites moved to gr8s.
Deploy from the dashboard or from CI with two environment variables, or run the same single container on your own infrastructure. Either way you keep control of your build and your data.
S3 is a free companion app where editors update meta tags, Open Graph data and schema without touching the code, and the changes go live through the same pipeline.
One price per site. Start free, upgrade when you want automation, more bandwidth and analytics. Founding prices are locked for life for early customers.
A single static or SPA site on your own domain.
Founding price, list 144 EUR. For production sites that deploy from CI.
Founding price, list 540 EUR. For high-traffic sites that need headroom and priority support.
The Pro plan is 96 EUR per year at the founding price, and self-hosting runs on a single server instead of per-request usage. Vercel Pro is 20 USD per user per month plus usage, and includes a wider platform. We keep the price low because we do less: a lean server with built-in SEO, not a full platform. The peer-reviewed benchmark measured about 5x fewer servers for the same workload, but your bill depends on how you host.
gr8s renders your exported SPA and analyses the resulting page for meta tags, headings, alt text, links and schema. The analysis runs inside the pipeline, so you get the score while building instead of from a separate crawler later.
Often yes, but be realistic: Next.js-specific features such as server components, ISR and server actions are not drop-in. A client-rendered Next.js app that can export as a static SPA is a much better fit.
We do not claim that. The peer-reviewed paper reports about 5x fewer servers, roughly 9.8x lower overall energy use, and lower memory (82.54 MB against 411.91 MB). We stick to what was measured.
Any framework that can export a single-page app: React, Vue, Svelte, Nuxt and others. The server itself is framework agnostic.
Yes. gr8s serves static sites too, and the SEO analysis runs on the rendered HTML regardless of how you generated it.
Every site ships a sitemap.xml and robots.txt. Pro sites notify IndexNow (Bing, Yandex, Seznam and Naver) whenever a page changes, so new URLs are re-crawled quickly instead of waiting for a periodic sweep. The build pipeline can also emit an llm.txt, a plain-text summary that AI assistants and answer engines can read directly.
Free sites get 5 GB a month on the volume network. Pro gets 50 GB a month on the standard network in Europe and North America. Scale gets 100 GB a month on the standard network across all regions. Usage is monitored with a soft alert, so a busy month raises a flag and an upgrade prompt, not a hard cutoff.
Free sites get lightweight, anonymised page counts. Pro and Scale get the full Plausible dashboard, included up to the plan's monthly event allowance. A site that outgrows its allowance is flagged so you can upgrade, and it is never silently dropped.
