The rendering layer should be open infrastructure

Open-source rendering infrastructure.
Self-host it. Own it.

Users see content.
Bots see nothing.

Modern sites render content with JavaScript. Browsers execute it. Search bots and AI crawlers don't, or do it poorly and inconsistently.

Your content exists. To them, it doesn't.

Users see content, bots see nothing

Our Journey

2020

Building at scale

Running a large JavaScript e-commerce platform. Discovering the rendering gap firsthand.

2023

AI crawlers emerge

The problem scales beyond our platform. Every JavaScript site faces the same challenge.

2024

EdgeComet begins

Development starts from scratch. Written in Go for performance and reliability.

2026

Open-source release

Apache 2.0 license. Self-host it, own it, contribute to it.

Built on production failures

Years of running rendering at scale taught us what breaks.
We designed around it.

Browser instability

Browsers aren't built for 24/7 service workloads. Memory grows, processes hang, crashes happen at the worst times.

Thundering herd

Popular URLs trigger dozens of simultaneous renders for the same page, spiking CPU and taking everything down with it.

Graceful degradation

If Chrome is unhealthy, bots should still get a response—not 5xx. Uptime isn't optional.

Open source is infrastructure

Linux, NGINX, Chromium, React, Vue, PHP, Go are all open source.
The rendering layer shouldn't be the exception.

Rendering executes your code

A renderer loads your pages and runs your JavaScript. That's not something you hand to a black box. You need to see exactly what it does.

Too critical for vendor lock-in

If rendering fails, bots see nothing. Your SEO and AI visibility drops to zero. That's not a risk you outsource.

EdgeComet is Apache 2.0-licensed. The self-hosted version is free forever.
A managed cloud option exists for teams that prefer not to run infrastructure themselves.

Built for modern JavaScript

No legacy code. No accumulated technical debt. Designed from scratch in 2024, released open-source early 2026.

Architecture

  • Written in Go for performance and reliability
  • Automatic browser pool management
  • Graceful degradation built in from day one
  • Three-service design with clear responsibilities

Framework support

  • React, Vue, Angular, Svelte
  • Next.js, Nuxt, Gatsby, Remix
  • Any JavaScript that runs in a browser

One goal: make your content visible.
To search engines. To AI systems. To every bot that matters.

The code is open.
Use it, fork it, or contribute.