There are no adapters and no special entry points. We read the manifest your project already carries, build it the way that ecosystem builds, and give the result its own URL in Europe.
Read from your package.json and built with the recipe that library needs. Nothing is rewritten, and there is no adapter to install.
The standalone build, server rendering and route handlers included.
The framework build, answered by its own request handler.
Content sites and islands, rendered on the server.
Deno's own framework, islands and all.
A fetch handler and nothing else. The smallest thing that answers.
The listen server you already wrote, bridged for you.
Modules, injection and pipes, on the Express platform.
Schema-first routes, through the same bridge as Express.
Middleware all the way down.
Any Vite server entry, streaming responses included.
Recognised on import. Its own build recipe is next.
Recognised on import. Its own build recipe is next.
Recognised on import. Its own build recipe is next.
Recognised on import. Its own build recipe is next.
Read from the manifest your ecosystem already writes. No Dockerfile needed, and if you have one it wins over anything we would infer.
TypeScript with no build step. Save a file and it is live.
Your package.json, your install, your start script.
A static binary on a distroless base, a few megabytes small.
C#, F# and Blazor, with Native AOT when you want the cold start.
Laravel and Symfony recognised, with Caddy workers when you want them.
ASGI or WSGI, from pyproject or requirements.
Gemfile in, Rails recognised, Puma serving.
A release build, and one binary out of it.
Maven or Gradle, and the JAR they produce.
An sbt build on the same JVM image.
A mix release with OTP inside it.
A rebar3 release, straight onto BEAM.
Typed, compiled, on BEAM.
Cabal or Stack, compiled ahead of time.
Your Dockerfile outranks anything we would infer.
No runtime at all. The router serves the files itself.
Three engines, all of them ours to run. Create one, link it to the services that should reach it, and the credentials arrive as environment variables.
Go beyond what seems possible.