#Introduction

Bay is a self-hosted application server for Alepha apps.

Where Cloudflare gives you someone else's serverless platform, Bay runs your apps as ordinary long-lived processes on a machine you own, with TLS, rollback and process isolation handled for you.

#When to use it

• You want a long-lived runtime: background work between requests, in-process caches, a local SQLite file.
• You would rather pay for one VPS than per request.
• The data has to stay on hardware you control.

#Deploying to it

Bay has no wrangler.jsonc equivalent. Everything it needs is already in the build manifest, so the target-specific story is one line of configuration:

1platform({2  environments: {3    production: {4      adapter: "bay",5      host: "deploy@bay.example.com",6      domain: "myapp.com",7    },8  },9});

Then alepha platform up -e production.

One more field matters on a non-default install: if Bay's root is not $HOME/bay-data, set socket to the absolute path of the control socket - without it, every command the adapter sends fails to find the server.

#Installing Bay

Bay is written in Go and ships as a static Linux binary on every release, for amd64 and arm64, alongside a SHA256SUMS file. Download the binary for your architecture from the GitHub releases, verify the checksum, and run it. The releases also expose stable releases/latest/download/bay-linux-<arch> URLs for scripted installs.