You built something, with Claude, with Cursor or by hand. This is where it goes online. You push, check the preview and take it live. The servers are in the EU, and you decide who sees the preview.
Access by invitation
The way
You get a token, push your repository, and the platform builds. Your coding agent can take every one of these steps. You can also take them yourself. What gets built is a project with a Dockerfile or a static site with an index.html.
You push, the platform builds. Every push builds, and what is on main wins. Whether the build succeeded is in the reply to the push.
Every change lands on a preview address first. You see it there. Who else sees it is your decision.
Once the preview is right, you take it live with one button. If something goes wrong, one button brings the previous version back.
Without an agent you need a token for your project and a second remote in your repository. Then git push.
What runs here
Each of them runs as an app on this platform, built and shipped like yours, as a container on port 3000, on preview first, then live. Most compute on your device and not on ours. transfer holds files for the recipient.
Spiral Galaxies, generated and solved in the browser.
A comparison sudoku that computes in the browser.
QR codes, generated on your device and not on ours.
Time tracking that computes on the device.
Handing over files. Sending needs an account, receiving does not.
Each of them has a Go backend. The platform's own services run in Go, Rust, Elixir and Java.
Who it is for
You built something with Claude or Cursor that works, and you want it online without learning hosting. You push, the platform builds and shows you the preview. You go live once you have seen it.
You want a website you maintain yourself. You see every change on a preview first, then you take it live.
You want to deploy and not run servers. What the platform needs from your code is five sentences on one page.
You look after several client projects. Each gets its own project here, with its code, its preview and its team, and the data of every project is in the EU.
Someone on your team maintains the website. The change is on the preview before anyone sees it, and the data stays in the EU.
Why here
Every component runs on servers in the EU, the machines in Germany, the object storage in Finland. No US cloud provider is involved, the CLOUD Act does not apply, and you do not have to explain US data processing to your clients.
earl.ee is built and shipped on earl.ee. Software mirrors the organisation that builds it (Conway's Law, 1967). Large cloud platforms mirror large corporations, their departmental boundaries become system boundaries, and you pay for that complexity. earl.ee has no departments.
Access
The platform is in alpha. It already carries its own development.
Access runs by invitation.
You get an invitation from someone who already works here.
Abuse: abuse@earl.ee · Security: security@earl.ee · Anything else: earl@earl.ee