Skip to main content

How this site works

Built by COLAB.
Running on Pantheon.

Pantheon is not just a reliable host for WordPress and Drupal. It runs Next.js applications too, with site management and engineering tools your team will love. The Agent-Ready Check is a Next.js app running on Pantheon. Here is how it is put together, how it talks to the services around it, and how we ship changes without risking the live site.

What happens when you run a check

  1. 01

    Pantheon serves the page

    The app is a Next.js application running in containers on Pantheon, behind a global CDN, with a cache shared across every container.

  2. 02

    The quick checks run on Pantheon

    Findable, Readable, Callable and Governed run while you watch, so the first results land within seconds.

  3. 03

    The browser agent runs on a worker

    Usable needs a real browser. The app hands that job to a worker through a queue, so the website itself stays fast.

  4. 04

    Results stream back

    The report fills in as each layer lands. Share it, and the report is emailed and the lead goes to the CRM with the consent you gave.

Connected to the services around it

Pantheon sits in the middle. Every connection it makes uses a secret stored per environment, so test keys never reach the live site and live keys never reach a test.

Orchestrates every service

Pantheon

Hosts the Next.js app, the CDN and the shared cache. Runs the Dev, Test, Live and Multidev environments.

  • Dev
  • Test
  • Live
  • Multidev

Keys stored per environment. Test keys never reach Live.

  • Pantheon to Supabase, carries reports + jobs

    Supabase

    Stores reports, the job queue and share submissions.

  • Worker to Supabase, carries pulls jobs, saves results

    Cloudflare Workers

    Runs the browser agent on a schedule, pulling jobs from the queue.

    Pantheon puts the job in the Supabase queue. The worker connects with its own key, stored in Cloudflare.

  • Pantheon to AI answer trackers, carries citation data

    AI answer tracking

    Best-in-class SEO, AEO and GEO trackers report how often AI answers link to a site.

  • Pantheon to SendGrid, carries report email

    SendGrid

    Sends report emails from an authenticated domain.

  • Pantheon to HubSpot, carries lead + consent

    HubSpot

    Captures CRM data for requested follow-ups.

Multidev

Every branch gets a real environment

This site was built in the open on Pantheon Multidev. Every change was reviewed on a working copy of the site before it went anywhere near Live.

  • Push a branch, get a URL

    A branch named multi-something, or a pull request, gets its own Multidev environment built from GitHub, with its own address. Our staging site is one.

  • Test on the real platform

    Each Multidev runs on the same Pantheon platform as Live, so a change that passes review behaves the same way in production.

  • Secrets per environment

    Real email and CRM keys live on staging only. Every other environment gets a placeholder, and test mode keeps every email in a test inbox.

  • Promote on purpose

    Code moves from Dev to Test to Live as a deliberate step, never as a side effect of a push.

Built for enterprise stability

  • Containers that scale out

    Pantheon runs Next.js in containers on Google Cloud and scales them horizontally as traffic grows.

  • A global CDN in front

    Pages and assets are served from the edge, close to every visitor.

  • One cache for every container

    Cached pages are shared across containers, so every visitor sees the same version.

  • Every change is a commit

    Next.js sites on Pantheon deploy from Git. There is no editing files on a live server, so every change has a history.

  • Heavy work kept off the web tier

    Long-running browser work happens on a separate worker, so a busy scan never slows the site.

Want your site to run like this?

Pantheon runs the platform. COLAB builds what runs on it. Find us both at the booth, or see how Pantheon hosts Next.js.