Node.js
18 · 20 · 22
Sites and APIs in JavaScript or TypeScript. Bun and Deno with a Dockerfile.
Technologies
Does your repository have a Dockerfile? We use it. If not, we recognize your language and build the site for you. Databases, cache and scheduled tasks are added in a few clicks.
16 results
18 · 20 · 22
Sites and APIs in JavaScript or TypeScript. Bun and Deno with a Dockerfile.
3.11 · 3.12 · 3.13
Web applications, APIs and background jobs.
8.2 · 8.3 · 8.4
Laravel, Symfony and WordPress, with the database alongside.
1.22 · 1.23
A lightweight binary that starts in an instant.
OTP 26 · 27
Phoenix and real time. Our own platform runs on Phoenix.
3.2 · 3.3
Rails, with Sidekiq for background jobs.
17 · 21
Spring Boot, Ktor. Plan for 1 GB of memory.
stable
Very light on resources once built.
Astro · Hugo · Vite
A file or a folder, or a generator that produces files.
15 · 16 · 17
Backups, 24-hour external access on request, read-only SQL console.
8.0 · 8.4
For WordPress and applications that require it.
8 · Redis
Cache, sessions, simple queues. Works with Redis libraries.
3
A file next to your service, backed up continuously with Litestream.
Docker Hub · GHCR
Run an existing image, with no code repository.
cron
A script run at a set time: reports, cleanup, reminders.
Compose v2
Several services at once; links follow your depends_on.
Not on the list yet? With a Dockerfile, almost anything works.
How we build your site
01
We build it as it is. You choose everything: version, system, dependencies.
02
We recognize your language (package.json, requirements.txt, composer.json…) and prepare the image.
03
HTML, CSS, images: served as they are, for free, with no server to run.
Not supported yet: graphics cards (GPU), Windows containers, sending email directly through port 25.