Skip to content
A-Line

Your website and apps in Europe, without the upkeep

Your websites, web apps and databases on servers in the EU. Push to GitHub and your changes go live on your own domain, with HTTPS.

Invite-only for now. We reply within 24 hours on working days.Already hosted somewhere else? During early access, we do the move for you.

  • Belgian company, EU servers

    A-Line Services is based in Belgium, and your apps and databases run in European data centres.

  • You talk to Arthur

    Arthur De Witte builds and runs A-Line.cloud, and answers your questions.

  • Updates and backups covered

    We keep the servers up to date, renew your HTTPS certificates and back up your databases.

Fix, ship and roll back from your AI assistant

A-Line.cloud has its own MCP server. Connect your AI assistant, and it reads your builds, deploys, domains, backups and bill, and redeploys or rolls back when you ask.

  • You sign in from the client: no API key to paste or leak.
  • It sees only the organisations you pick, with your role in each.
  • Secret values never reach it, and logs are redacted.
  • You revoke it any time under Connected apps.

Set up from Claude, Claude Code, Cursor, Codex or VS Code. Included at no extra charge.

See everything it can do

Fix a build, merge it, watch it go live

~/sites/dentist-siteClaude Code

You: the dentist-site build failed after my last push, can you fix it?

a-line - list_builds (MCP)(app: "dentist-site", limit: 3)

b_214 failed in the build step, 07:58Running

a-line - get_build_log (MCP)(build: "b_214")

Read 48 linesRunning

[ERR_MODULE_NOT_FOUND] Cannot find package
'@astrojs/sitemap' imported from /app/astro.config.mjs

Update(package.json)

Added @astrojs/sitemap to dependenciesRunning

Bash(pnpm build)

Built 24 pagesRunning

Bash(gh pr create --title "Add the sitemap package")

Opened pull request #87Running

astro.config.mjs imports @astrojs/sitemap, but it was never added to package.json, so the build stopped. It builds here now, and pull request #87 is open. Shall I merge it once the checks pass?

You: yes, merge it when it's green

Bash(gh pr checks 87 --watch)

All checks passedWaiting for checks

a-line - list_actions_jobs (MCP)()

test ran on a-line-4vcpu in Germany, 1m 12sRunning

Bash(gh pr merge 87 --squash)

Merged into mainRunning

a-line - list_builds (MCP)(app: "dentist-site", limit: 1)

b_215 from main, builtBuilding

a-line - list_deploys (MCP)(app: "dentist-site", limit: 1)

Release 42 liveRunning

Merged. The checks ran on your A-Line runners and passed in 1m 12s. dentist-site deploys on every push to main, so build b_215 started on the merge, and release 42 is live.

Check on your client sites

Claudea-line

You: Anything I should know about my client sites this morning?

a-line get_overview12 apps: 11 running, 1 build failedRunning
a-line list_buildsFailed at 07:58, nothing releasedRunning

11 of your 12 apps are running as usual. The dentist-site build from 07:58 failed, so the site still serves yesterday's version: visitors see no difference.

You: Is the bakery's new domain live yet?

a-line list_domains1 domain, waiting for DNSRunning

Not yet. The domain doesn't point to A-Line.cloud, so its certificate is waiting. Add the DNS record the console shows for it at the registrar, and the certificate follows on its own.

You: And is the webshop's database backed up?

a-line list_backupsDaily at 03:00, 14 keptRunning

Yes. shop-db is backed up every night at 03:00 and the last 14 backups are kept, in the EU. Last night's finished at 03:04.

Roll back two apps, then find the bug

AgentCursor

You: Checkout throws errors since this morning's deploy. Roll the shop back, then find what broke.

list_deploys app: "shop-web", limit: 210:42 live, 08:15 before itRunning
list_deploys app: "shop-api", limit: 210:40 live, 08:12 before itRunning
redeploy_previous app: "shop-web"Back on 08:15Running
redeploy_previous app: "shop-api"Back on 08:12Running
Grep "total" src/3 matches in checkout.tsRunning
Edit src/lib/checkout.tsSends amount instead of totalRunning

Both apps are back on this morning's earlier releases, so checkout works again. The cause: the 10:40 API release renamed total to amount, and the shop still sent total. I've fixed checkout.ts.

You: Looks right, push it.

Bash git pushPushed to mainRunning
get_app_status app: "shop-web"Running the new releaseDeploying
get_app_status app: "shop-api"Running the new releaseRunning

Pushed. Both apps built from main and run the new releases, with the fix and the renamed field together.

Find what drives the CI bill, then fix it

~/sites/client-sitesCodex

You: our Actions spend jumped this month, what's going on?

Called a-line.get_actions_usage(period: "30d")

e2e: 68% of the minutes, on a-line-16vcpuRunning

Called a-line.list_actions_jobs()

e2e ran 214 times, on pushes to every branchRunning

Read .github/workflows/e2e.yml

Runs on every push, to any branchRunning

Most of it is e2e. It runs on a 16 vCPU runner for every push to every branch, so a branch with an open pull request is tested twice for each push. Running it on pull requests and on main only would drop about half of its runs. Shall I change that?

You: yes, open a PR for it

Edited .github/workflows/e2e.yml (+4 -2)

Runs on pull requests and pushes to mainRunning

Ran gh pr create --title "Run e2e once per change"

Opened pull request #31Running

Ran gh pr checks 31 --watch

All checks passedWaiting for checks

Pull request #31 is open and green. Once it's merged, e2e runs once per change instead of on every push, on the same runner.

Why we built it

Software that runs all day, like a web shop, a booking system or a nightly job, usually ends up in one of two places. Both cost you something.

An app platform that bills by use

Quick to start. But you pay for every hour your app runs, so an app that never stops gets expensive. Running a second copy to keep it up doubles that bill.

Your own servers

Cheaper per server, but someone has to set up Kubernetes, configure every server and app, keep it all updated and secure, and fix it when it breaks. For a small team, that is a job of its own.

What we built instead

Servers reserved for you, priced per server. Your apps run on them all day without a bill of their own, and nobody on your side has to look after the servers.

  • Your app can run as several copies, so it keeps serving while one is replaced or a server is maintained.
  • If a database server fails, a replica on another server takes over.
  • When your apps need more room, servers can be added automatically, up to the limit you set.
  • Keeping the servers updated and secure is our job.

How it works

Your developer sets it up once. After that, every change goes live by itself, and you can always see what is running.

  1. Connect your code, once

    Your developer links the app's GitHub repository to A-Line.cloud. That is the whole setup.

    Your developer: A Dockerfile, or a preset for Next.js, Remix, SvelteKit or Nuxt.

  2. Every change goes live

    New opening hours? Your developer pushes the change and it goes live on your own domain, with HTTPS. Nobody uploads anything by hand.

    Your developer: Push to main. A-Line.cloud builds the new version and rolls it out.

  3. See what runs, and go back

    You always see which version your visitors get. If a change goes wrong, the previous one is back in one click.

    Your developer: Logs and metrics per app. Every earlier deploy is kept, so you can always roll back.

Prefer to keep your setup in Git?

You can. Describe each app in a short A-Line definition file next to your code. It is optional: everything also works from the console.

projects/shop/apps/web.yaml
version: 1
source:
  git:
    repo: example/shop-web
    branch: main
port: 3000
triggers:
  on: push

Will my app run here?

Most likely. Here is what runs today.

Your apps

  • Container apps from a Dockerfile
  • Next.js, Remix, SvelteKit and Nuxt
  • Static sites
  • Scheduled jobs

Your data

  • PostgreSQL, with replication
  • Valkey, ClickHouse and NATS
  • Object storage (S3-compatible)
  • Databases with scheduled backups

Around it

  • Your own domains, with HTTPS
  • Rolling deploys and rollback
  • Logs and metrics
  • Autoscaling

Not on the list? Ask before you apply. Ask about your stack

CI from €0.002 a minute

Your GitHub Actions jobs run on a fresh machine in the EU. You change one line in your workflow and keep every step, action and secret as it is.

  • A fresh machine for every job, deleted when it ends.
  • Jobs run only in the EU: France, Germany and Poland.
  • You pay per started minute. Time in the queue is free.

The CI of this website runs on a-line-4vcpu.

See the runners and prices

Safe and European

What happens to your apps and data once they run here.

Where your data lives
Your apps, databases and backups stay on servers in the EU, in data centres certified to ISO/IEC 27001.
Kept apart
Your apps and databases run on your own cluster, with your own servers and network. No other customer's workloads run on it.
What is shared, and what is not
Backed up
Databases get scheduled backups, kept for as long as you choose. PostgreSQL runs with replication.
Signing in
Protect your account with a passkey, or a code from an authenticator app.

Everything about Europe, data and security

No surprises

What you pay, and what happens if you ever want to leave.

What it costs

You pay for the servers reserved for you, and run as many apps on them as fit. You pay in advance, in euro, and we email you when your balance runs low, and again before anything is paused.

See pricing

Leaving is easy

Your app runs from a standard container image, your databases are plain PostgreSQL and your files sit in S3-compatible storage. You can take all of it elsewhere.

How leaving works

Who is behind it

A-Line.cloud is built and run by A-Line Services, a software company in Belgium. Arthur De Witte builds the platform and answers your email.

About A-Line Services

Need hands as well as a platform? See our services

Questions people ask

Something else on your mind?

Write to us and Arthur replies, within 24 hours on working days.

hello@a-line.be

Or see the contact page

Who is A-Line.cloud for?

SMEs that want their website, web apps and databases in Europe without running servers themselves. Someone still builds your software, in-house or a freelancer; we take care of where it runs. If nobody builds it yet, A-Line Services can.

Where is my data kept?

In the EU. Your apps, databases and backups run on servers in data centres certified to ISO/IEC 27001. That certificate belongs to the data centre operators, not to A-Line Services.

Is anything shared with other customers?

Your cluster is not. Your apps and databases run on your own cluster, with its own servers and its own network, and no other customer's workloads run on it. Two platform services are shared: builds and file storage. Each build runs in its own isolated environment that is thrown away afterwards, never on your cluster. Your files sit in shared storage, with keys that only open your own buckets.

Can you move my existing apps?

Yes. During early access, we do the move for you. When you request access, tell us what you run today and where, and we plan the move with you.

More about billing and the balance on the pricing page

Ask an AI what it makes of us

Each link opens an AI assistant with a question already filled in. It asks the assistant to read this site, weigh up A-Line.cloud honestly, and say what it couldn't check.

Some assistants ask you to sign in first.

How do I get in?

A-Line.cloud is invite-only while we take on new customers one at a time. Here is what happens.We reply within 24 hours on working days.

Request access

Already hosted somewhere else? During early access, we do the move for you.

  1. Today

    You tell us who you are

    A few lines about you and what you want to run.

  2. Within 24 hours on working days

    We reply

    With questions, or with your invite.

  3. After your invite

    You go live

    Sign in, and we help you with your first deployment.