Architecture
Every piece between your users and your data. Select a component to look inside.
Eurobase usersConsole · CLI · API
Teams building on Eurobase work from the console, the CLI or the API.
One front door, protected like everything behind it.
Project users
The people using your apps, on eurobase.dev subdomains or your own domains.
Their traffic follows its own path, isolated from the console.
WAF
Filters malicious and abusive requests before they reach anything else.
Attacks cost no compute, and blocked requests never reach your bill.
Load Balancer
Spreads console and API traffic across healthy instances.
Releases roll out without dropping requests.
Web containereurobase.dev
Serves this site and the console, rendered on the server.
Keys and tokens never reach the browser.
API containerapi.eurobase.dev
The control plane: projects, deployments, builds, usage and billing.
One source of truth for everything the console and the CLI do.
Load Balancer
A dedicated entry point for the traffic of your projects.
Your apps never compete with the console for capacity.
Reverse proxyYour domains
Terminates TLS and issues certificates for your domains automatically.
HTTPS everywhere, with nothing to configure.
Eurobase GatewayBuilt in-house
Our own gateway routes every request, checks access and limits, and records usage before your code runs.
Routing, protection and billing you can trust, in a single hop.
PostgreSQL + KV cache
PostgreSQL holds the state of the platform; a key-value cache keeps the request path fast.
Private by design, never reachable from the internet.
Project runtimesWorkers · Containers · Functions
Your code runs on a private network, reachable only through the Gateway.
Nothing you deploy is exposed directly to the internet.
Object StorageS3-compatible
Stores build artifacts, releases and the files of your projects.
Every release stays available for an instant rollback.