CloudFront
Global entry point. Serves cached assets from the nearest location and forwards page requests to the origin over TLS.
viewer → cloudfront
Ajna · SSR hosting
Dynamic sites that render on the server and load from the edge.
Ship Next.js on Ajna's serverless platform. Real HTML in the first byte for search and link previews, fresh data on every request, and no servers to keep running.
Render receiptLIVE
This page rendered
on the server.
RENDERED AT2026-08-08T19:53:51.028Z
REGIONap-south-1
CONTAINERWARM
REQUEST88b6b513…6dff
ORIGINAPI Gateway → Lambda
BACKENDGET /api/health · 200 · 35ms
Printed server-side for this request. Refresh to reprint — the timestamp and request id change every time.
In the HTML
Findable by default
Titles, meta, and Open Graph tags arrive fully rendered — so crawlers and shared links see real content, not an empty shell.
Fresh per request
Never stale
Every visit renders live against your data. No rebuild to publish a change, no cache to bust.
One function
Nothing to run
A single Node server on AWS Lambda behind CloudFront. It scales to zero when idle and out under load.
The request path
One request, three jobs — handled where each is fastest.
Static bytes come from the edge, the page renders in-region next to your data, and CloudFront ties it together under one domain.
Node on Lambda
Next.js renders the page in-region, right next to your data. Warm containers answer in single-digit milliseconds.
cloudfront → api gateway → lambda
S3, content-hashed
JavaScript and styles ship immutable from S3 with long cache lives — updated safely on every deploy.
/_next/* → s3
Give it a public surface.
Point a domain at Ajna and ship a server-rendered site that search engines and shared links actually read.