Hosted and operated in the EU

Push your code.We build it, host it and protect it.

Ship from GitHub to EU infrastructure. Firewall, vulnerability alerts and incident detection included, at one fixed monthly price.

acme-shop · deployment
Example deployment: an app is built from GitHub, deployed with HTTPS, and a malicious request is blocked shortly after it goes live.

Follow one app from first push to production.

acme-shop is a small Node.js web shop with a PostgreSQL database. Here's everything that happens to it on Apply.Build, without anyone writing a line of infrastructure config.

01 Deploy

From GitHub to a live URL in one push.

Connect your repository and pick a branch. Apply.Build detects your language and builds your app automatically. Node.js, Python, Go, Java, PHP, Ruby, Rust and 14 more are supported, or you can bring your own Dockerfile. Every push to that branch deploys a new version.

  • HTTPS out of the box. Certificates are issued and renewed for you, on our domain or up to 10 of your own.
  • Undo a bad release in one click. Roll back to any of your last five deployments. It's fast because nothing is rebuilt.
  • Know when a build finishes or fails. Notifications go straight to Slack or Discord.

02 Protect

Bots start probing your app as soon as it's online.

Automated scanners crawl the internet looking for new sites. They search for exposed config files and password files, try common passwords on login forms, and send malformed requests hoping to reach your database. Apply.Build puts a web application firewall (WAF) in front of every app. It filters this traffic before it ever reaches your code, and there's nothing to configure.

  • See who's attacking. A live view shows blocked requests, where they come from, and what they tried.
  • Your app runs in its own sealed box. Each app gets its own micro-VM, a lightweight virtual machine. A compromised app next door can't reach yours.

Elsewhere: a separate firewall service with its own setup and bill.

More about the firewall
apply.build/app/security

03 Patch

Most of your app's code was written by someone else.

acme-shop depends on hundreds of open-source packages. When a security flaw is found in one of them, your app is exposed until you update, and nobody tells you. Apply.Build continuously checks every package your app ships with. When a flaw turns up, you're told which app is affected, which package causes it, how serious it is, and which version fixes it.

  • A full list of what's inside your app. We record every package in each build, in a format known as an SBOM (software bill of materials). It's the inventory customers, auditors and the EU Cyber Resilience Act increasingly ask for.
  • Alerts where you already work. Vulnerability alerts go to Slack or Discord.

Elsewhere: a separate dependency-scanning tool.

More about vulnerability scanning

04 Detect

When acme-shop breaks, you get one alert that says why.

A release goes out and acme-shop starts running out of memory. It crashes, restarts and crashes again, and checkout requests start failing. Apply.Build watches your app's logs, metrics, traces and restarts, connects the signals that belong together, and opens one incident that says what's wrong. It reaches you in Slack or Discord, and closes itself once your app recovers.

  • Nothing to set up. No SDK, no agent, no log format to follow. It works from your app's first deploy, on every plan.
  • Any log format. Plain text, JSON or stack traces: errors are picked out and grouped, so 341 copies of one error read as one.
  • Metrics, logs and traces included, with response times and errors broken down by endpoint.

Elsewhere: an error-tracking service, and its SDK in your code.

More about incident detection

05 Store

Your database next to your app, on the same platform.

Create a managed PostgreSQL database, or Valkey for caching, from the same dashboard and connect acme-shop to it. Its metrics and connected apps show up next to your app, and the data never leaves the EU.

  • Undo a bad migration. Restore your database to any moment in the last 7 days, on every plan.
  • Stay up if a server fails, with replicas that take over from the primary.
More about databases

Here, all of that is one service. Elsewhere, it's a stack.

You've just seen what acme-shop gets on Apply.Build. On most platforms, the same setup means signing up for extra services to block attacks, catch vulnerable dependencies and tell you when your app breaks, each with its own setup, its own bill, and often its own US jurisdiction.

Compare with:
On Heroku
On Apply.Build

Hosting

Somewhere your code runs and stays running.

Standard-2X dyno€44 / mo
1 resource package€5 / mo

Protection from attack traffic

Bots probe every public app for weak spots, around the clock.

Cloudflare Pro€18 / mo
Included

Alerts on vulnerable dependencies

Most of your code is open-source packages, and new flaws are found in them every week.

Snyk Team€22 / mo
Included

Alerts that say what broke

Errors, crashes and slow endpoints, connected into one alert instead of a pile of signals.

Sentry Team€23 / mo plus its SDK in your code
Included, no setup

Request metrics

Response times, status codes and request rates show something broke before your users tell you.

Included
Included

HTTPS and custom domains

Browsers flag sites without it, and certificates expire.

Included
Included

EU jurisdiction

Who can legally demand access to your data.

US company, US law applies
European company, EU law
What you end up with
4 servicesfrom €107 / month4 separate bills
1 service€5 / month1 bill

Hosting is each platform's closest plan to 1 vCPU and 1 GiB of memory, in its lowest-priced region. Other services are the cheapest paid plan of a common tool for each job. USD list prices, converted at the ECB reference rate (1 EUR = 1.1298 USD) and rounded. Checked October 2026. Full comparison with Heroku

One service. One invoice. One jurisdiction.

Where your servers are isn't the whole story. Who owns them matters too.

US law, including the CLOUD Act and FISA 702, lets US authorities demand data from US companies even when that data is stored in Europe. An EU region from a US provider doesn't change who they answer to. Apply.Build is run by Codebite Oy, a Finnish company, on European infrastructure. Your app, its database, its logs and its backups stay in the EU, under EU law and GDPR.

Visitors

Your users

GitHub (US)

Source code, pulled to build

EU · run by Codebite Oy · EU law

Firewall (WAF)

Filters attacks

Your app

In its own micro-VM

PostgreSQL

Your database

Logs, metrics

And backups

Billing only

Stripe

Payments, EU and US. No app data.

Everything inside the EU box is run by Codebite Oy. Dashed boxes are services outside Apply.Build.

Where data goes, specifically

Your running app, database, logs, metrics, backups
Where: Finland
Operated by: Codebite Oy, on dedicated bare-metal servers
Your source code
Where: Your GitHub repository. We pull it to build in Finland.
Operated by: You, and GitHub
Payment details
Where: EU and US. No application data ever passes through it.
Operated by: Stripe

Our full sub-processor list is public, and we tell you before adding or replacing one. See the sub-processor list

Exactly what you get, and what's not here yet.

21 languages detected from your repository, or bring your own Dockerfile. Static sites too.

  • Node.js
  • Python
  • Go
  • Java
  • PHP
  • Ruby
  • Rust
  • C#/.NET
  • F#
  • Elixir
  • Deno
  • Scala
  • Clojure
  • Swift
  • Dart
  • Haskell
  • Crystal
  • Gleam
  • Zig
  • COBOL
  • Lunatic

Build and deploy

  • Language detected automatically, or your own Dockerfile
  • Every push to a chosen GitHub branch
  • Roll back to any of the last 5 deployments

Security

  • WAF on every app
  • Dependency scanning with an SBOM for each build
  • Each app in its own micro-VM

Monitoring

  • Incident detection from logs, metrics, traces and restarts
  • Response times, status codes and request rates
  • Build logs, app logs and request traces

Notifications

  • Slack and Discord
  • Incidents, builds, deployments, status changes and vulnerabilities

Data

  • Managed PostgreSQL with failover replicas
  • Restore PostgreSQL to any moment in the last 7 days
  • Managed Valkey, Redis-compatible

Domains and sizes

  • HTTPS on every app, up to 10 custom domains
  • 0.25 vCPU and 256 MiB up to 2 vCPU and 2 GiB per app
  • Ephemeral disk per app, 2.5 to 20 GB

Coming next

In the works

Object storage

Files and uploads that persist across deploys.

Need something else?

Tell us. Early users shape what we build next.

See every feature. Full limits and runtime versions are in the docs.

Your bill is known before the month starts.

You buy resource packages at €5 a month each. One package is 1 vCPU, 1 GiB of memory and 10 GB of storage, and you split it across your apps and databases however you like. There's no usage billing, and traffic spikes don't show up on your invoice.

Free tier: 0.5 vCPU and 512 MiB

No credit card. It stays active when you add paid packages, and after you cancel them.

acme-shop · monthly bill

Same every month

  • Web shop

    Medium · 1 vCPU, 1 GiB · 1 package

    €5.00

  • Background worker

    Tiny · 0.25 vCPU, 256 MiB · 0.25 of a package

    €1.25

  • Staging copy

    Tiny · 0.25 vCPU, 256 MiB · 0.25 of a package

    €1.25

  • PostgreSQL database

    Small · 0.5 vCPU, 512 MiB · 0.5 of a package

    €2.50

Total

2 packages × €5.00

€10.00

Included, with no separate line on your bill

  • Firewall
  • Vulnerability alerts
  • Metrics
  • Logs
  • HTTPS
  • Custom domains
  • EU hosting
Price the same stack elsewhere

Questions people ask before moving their app

Still have a question?

Ask the founders directly. Contact us

Push your next app. We'll take it from there.

Deploy free in a few minutes. Questions about moving an app from Heroku, Render or elsewhere? Talk to us.