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. 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.
Most teams reach for Vercel and Next.js, or keep a static host and bolt SEO on afterwards with a separate crawler. gr8s is positioned against all three, and against doing nothing.
One command adds the gr8s toolkit and the S3 SEO Studio to your project.
Export your frontend as you already do and let the CLI analyse the build and prepare the SEO datasource.
Push to managed hosting from CI, or run the single Docker image on any server.
# install pnpm install -g @codomatech/gr8s-tools # prepare the SPA (any framework) pnpx gr8s-cli -f dist/index.html # deploy managed, or self-host 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.
gr8s ships as a single container, so you can host it on any cloud you already use and keep control of your own infrastructure.
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.
Start free. Pay only when you want managed hosting with a custom domain and API deploys.
Host a static or SPA site on a free gr8s address.
For production sites that need a custom domain.
Hands-off migration and tuning for complex apps.
For self-hosted use it can be, because you pay for a server instead of per-request usage. The managed plan is 48 EUR per year. 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.
