gr8s serves your exported SPA or static site and merges in the SEO content its Studio wrote for you — titles, meta tags, Open Graph and schema — as a data source, so crawlers get real HTML without server-side rendering. One product for hosting, SEO authoring, analytics and CDN deploy: let us run it, or self-host the same single image.
Hosting, SEO authoring, analytics, CDN delivery and CI deploy in one product and one price. It replaces a host, a paid SEO audit tool, a separate analytics service, and the glue that holds them together — one login, one bill, one thing to maintain.
Your SEO content lives in a data source: per-URL titles, meta descriptions, Open Graph tags and schema. S³ Studio writes it by rendering and scoring your site, you edit it, and the server merges it into the HTML it serves. No SSR, no server components, no separate audit tool.
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. That leaner footprint is what lets us price hosting flat and low.
Build your app on the client, export it, and let gr8s serve it with your SEO content merged in. 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 built-in, real-time analytics dashboard inside 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. Others assemble a stack from several services. 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.
S³ Studio renders your site, scores every page and writes a data source of SEO content — titles, meta descriptions, Open Graph and schema — that you edit. This is where the SEO work happens; the server only applies the result.
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 server merges your build with the data source, with a CDN and deploy pipeline included.
Prepare the build once with the CLI, then serve it with the single gr8s image 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 ITIS 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 small 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.
gr8s is one product — hosting, SEO authoring, analytics and CDN deploy — for a flat 96 EUR a 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 you still add an SEO audit tool and an analytics service on top. We keep the price low because we do the work smarter, not because we do less: the peer-reviewed benchmark measured about 5x fewer servers for the same workload, and that leaner footprint is what makes a flat, lower price possible.
gr8s serves your exported SPA and merges in SEO content from a data source: per-URL titles, meta descriptions, Open Graph tags and schema. S³ Studio produces that data source by rendering and analysing your site, and the server applies it to the HTML it serves. The analysis and authoring happen in the Studio during your workflow, not in the request path — which is why there is no SSR and no server components to maintain.
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. You author the SEO content in S³ Studio exactly as you would for an SPA, and the server merges it into the static HTML.
Typically a static host or a platform plan, a paid SEO audit tool, a separate analytics service, a crawler or prerender service, and the CI glue between them — each with its own bill, login and failure mode. gr8s covers hosting, SEO authoring, analytics, CDN deploy and crawling in one product and one price.
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.
The free plan is for static or small SPA sites up to 20 MB. Pro raises the deployed build size to 2 GB and Scale to 10 GB. The limit applies to the built site you deploy, not your source repository.
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 200 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 includes 1,000,000 analytics events a month with 12 months of history; Scale includes 10,000,000 a month with 24 months of history. If a site reaches its monthly allowance, analytics collection pauses until the next month or an upgrade and the site is flagged — the website itself never goes offline, and you are never asked to run a second analytics tool.
