A high-performance web server that lets you serve multiple static websites from different S3 buckets through a single server. It's perfect for managing multiple static sites with their individual domains while keeping the hosting simple and efficient.
It uses Tigris for object storage and benefits from its global caching.
Bun-tastic uses Fly.io as its default deployment option, allowing you to set up global compute with a single command.
In other words, it's a high-performance, scalable, and efficient solution for hosting multiple static websites on your own terms.
📚 Tip: Use GitHub's table of contents feature to navigate this document easily! Click the menu icon next to the README title above.
- Serve multiple static websites from one application
- Global distributed caching and compute
- Easy configuration through JSON
- Brotli & zstd compression (via Fly Proxy), with response streaming
- Built-in monitoring with Grafana dashboard (via Fly)
- Smart path handling with automatic index.html resolution
- Built on Bun's native S3 client and web server, thereby benefiting from Bun's fast performance
- It's Lightweight. It uses zero dependency and can run on a single CPU with 256MB RAM
- Posssibility to add and configure middleware and that can handle extra needs like authorization, redirect/rewrite rules, etc.
- Possible cheap/affordable hosting with volume-based licensing on Fly and affordable Tigris storage.
- CLI/API for simplified site uploads (with resumability)
- Per-machine/VM caching with cache invalidation (potential performance boost)
- 103 Early Hints support (more efficient page load times)
- Easy setup/config to run on multi-cores
- Configurable bot request blocking
It's fast! But better to try it for yourself. Here's a sample from a local test:
You can see that the response time is very low and more than have returned in less than 100ms, for a response of 6KiB in size. Now deploy this in the regions you want to get lower latency and faster response times.
The server is a shared VM with 256MB RAM and 1 CPU running on fly.io. Deployed region is in Sweden (arn). Tested on a 2021 MacBook Pro with M1 chip. Average internet speed 200 - 300Mbps. Try it yourself at https://first.flycd.dev or https://second.flycd.dev
Here's a video of me sampling the load and response times:
Here's a video showing how to use it with the CLI (Quickstart demo):
Click to watch the video
- Bun >= 1.2.0
- S3-compatible storage (like Tigris). Tigris is recommended for its global/distributed caching support.
- An account on Fly.io (optional)
- Clone this repository
- Copy config.example.json to config.json:
cp config.example.json config.json
- Update config.json with your domain to bucket mappings:
{ "example.com": "my-bucket-name", "another-site.com": "another-bucket-name" } - If you intend to run it local, copy
.env.exampleto.envand fill in your S3 credentials:cp .env.example .env
- For Fly.io deployment, add the secrets to the env after you deployed or created the app. You can add it from the dashboard or CLI. Here is an example using CLI:
fly secrets set AWS_ACCESS_KEY_ID=<KEY_ID> AWS_SECRET_ACCESS_KEY=<ACCESS_KEY> AWS_REGION=auto AWS_ENDPOINT=https://fly.storage.tigris.dev
To run bun-tastic locally ensure you have the minimum required version for Bun (Bun >= 1.1.43), the correct .env file and values, and the config (config.json).
Once you have confirmed that you have all of that in place, run bun index.ts to start the server.
You can configure a local domain in
/etc/hostsand use a tool like Caddy to proxy the requests to the local server.
There's a sample fly.toml file in the repo, i.e. fly.example.toml. Rename it to fly.toml or create your own fly.toml file with same content. Edit it and set the name for the app, and optionally change the machines type (or other settings) to match your needs.
# uncomment below and specify the name for your app
- # app = 'bun-static-host'
+ app = 'your-own-app-name'
# specify the primary region for your app
primary_region = 'arn'
[build]
[http_service]
internal_port = 3000
force_https = true
auto_stop_machines = 'stop'
auto_start_machines = true
min_machines_running = 0
processes = ['app']
[[vm]]
memory = '256mb'
cpu_kind = 'shared'
cpus = 1Then run fly launch --no-deploy to launch/scaffold the project.
Next, set the secrets using the command in case you haven't done that already:
fly secrets set AWS_ACCESS_KEY_ID=<KEY_ID> AWS_SECRET_ACCESS_KEY=<ACCESS_KEY> AWS_REGION=auto AWS_ENDPOINT=https://fly.storage.tigris.devFinally, run fly deploy to deploy the app.
You can scale the app to multiple machines and regions if needed (see docs for details).
For the domain configuration, you'll need to set up DNS records for each domain you want to serve. Fly.io can handle TLS certificates for you, but you'll need to set up the DNS records to point to the app's IP address or Fly's subdomain.
You'll find more info on how to do this in their docs. If you use Cloudflare for DNS, make sure you read this section in that page.
While you can upload files to your bucket using the web console from Tigris, or the AWS CLI, you can also use the Buntastic CLI to upload files to your Tigris/S3 bucket. It is designed to be simple to use, and also uploads faster compared to the other options.
You can use the CLI for your daily task, or use it in your CI/CD pipeline.
More details about how to install and use it can be found in the CLI's README.
Here are some common questions and answers.Please, if you have more question or have doubts/critic, please start a discussion :)
It's fine to use traditional hosting service but if you're looking to selfhost your own static sites from a single (or distributed) machine, this is FOR YOU.
You have the flexibility to configure as much redirect/rewrite rules as you want. You could also add authorization/authentication rules to specific domains and routes, which can help you share content with specific users.
It's ideal for agencies, freelancers, or individuals who have many clients and projects, and they can easily manage them from one server and save cost.
It depends on your usage.
If you have just one website that gets a few hundred visits per day, it's probably cheaper to use a traditional static site host. However, if you have multiple websites or a high traffic site, self-hosting can be more cost-effective.
When you combine the flexibility and control of self-hosting, with the affordable cost of Tigris storage, volume-based licensing on Fly.io, and the ability to scale to zero, then you can save a lot of money.
See the benefits section.
Yes, any S3-compatible storage service will work.
Feel free to open pull requests if there's an issue! Use GitHub Discussion for feature requests or to discuss the project or potential defects.
If you find this project useful, please consider sponsoring it. Your support helps me continue developing and maintaining this project. I haven't set up a Patreon or similar platform yet, but I'm open to suggestions. In the meantime, DM me on Twitter/X, LinkedIn, or Bluesky.