Skip to content
excalibase
sites
Sitesbeta

Sites

Sites hosts the static build of a frontend. You build it wherever you like (Vite, Next.js static export, plain HTML), upload the output folder as a .tar.gz, and it is live at <name>.excalibase.app. It shipped in v1.6.0.

Sites serve files only. Anything that needs a server belongs in edge functions or a container.

Create a site

  1. Open your project in Studio and go to Sites.
  2. Choose New site and enter a name. It becomes the first part of the address, so it is 3 to 63 lowercase letters, digits or hyphens, with no two hyphens in a row. Names such as www, api, admin and anything containing excalibase are reserved.
  3. Tick Single-page app if your app has client-side routes. Unknown paths then load index.html; with it off, they get your 404.html. You can change this later.

Deploy a build

Studio takes the build output as a .tar.gz (or the build folder itself) with index.html at its root. Packing a Vite build looks like this:

npm run build
tar czf site.tgz -C dist .

Choose Upload .tar.gz on the site's page. The deploy is live as soon as it is published, and the site keeps its history, so any earlier deploy can be rolled back to with one click. A rollback also restores the single-page-app setting that deploy was published with.

Deploy from CI

For automatic deploys, create a deploy token on the site's page. It can deploy that one site and read its deploys, and nothing else. It expires after 7 to 365 days (90 by default) and is shown once. Store it as a secret named EXCALIBASE_DEPLOY_TOKEN, then upload the archive as the raw request body:

curl --fail-with-body -sS -X POST \
  "https://app.excalibase.io/api/projects/$PROJECT_ID/sites/$SITE_ID/deploy?label=$GITHUB_SHA" \
  -H "Authorization: Bearer $EXCALIBASE_DEPLOY_TOKEN" \
  -H "Content-Type: application/gzip" \
  --data-binary @site.tgz

label is optional and names the commit in the deploy history. The call answers once the deploy is live, or with an error status if it failed. The site's page has ready-made GitHub Actions, GitLab CI and Jenkins files that build, pack and upload for you.

Custom domain

  1. On the site's page, open Custom domains and add a hostname such as www.example.com. It must be a subdomain, not a bare domain like example.com.
  2. Pick how the certificate is validated: HTTP needs only a CNAME, while TXT lets the certificate be issued before you move DNS.
  3. Studio lists the exact records to add at your DNS provider, with a CNAME that points to Excalibase. Add them.
  4. The domain shows Waiting for DNS until the records are seen and a certificate is issued, then Live. This is checked every few minutes. A domain that is not live within seven days is removed.

Keep the records in place afterwards: the domain is checked again every hour and stops serving once a record is gone.

Limits

On the Free plan a project can have 5 sites and 2 custom domains and can start 30 deploys an hour. A deploy holds up to 20,000 files, 25 MB per file and 100 MB in total. These limits may change during the beta; Sites in Studio shows the ones that apply to your project.

Self-hosting

Sites are served from Cloudflare's edge, so a self-hosted install needs its own Cloudflare account and is off until you configure it. Without that, the rest of the platform works and the Sites page is not offered.