App hosting

Host the sites Stride did not build

Point a project at a Git repository with a React, Astro, Next.js, SvelteKit or Nuxt app. The same installation that serves your Stride sites builds it, serves it, and keeps the previous build to go back to.

Builds in their own box

A separate builder process runs git and npm with its own memory limit, and never sees your server's secrets.

Instant rollback

Every deployment is immutable and numbered. Promoting or rolling back is one column in the database, so it takes a moment.

Previews per branch

Every build has its own permanent address, so you can share a branch before it goes live.

Custom domains and HTTPS

Add a domain, point it here, and Stride can obtain the certificate itself.

Server-rendered apps

Next.js, Nuxt and SvelteKit in their default modes get a Node process per live deployment.

Counted like any page

Hosted pages show up in Stride's server-side analytics, with no script added to your build.

Honest status

Optional, and newer than the rest

Hosting is a build feature, not part of the npm package: it needs a build from source with --features hosting. Static sites are verified end to end; GitHub deploys, certificates and the Node runtime are built and tested, and are being proven on real traffic.

$ cargo build --release --features hosting,plugins

$ stride serve

$ stride builder --db ./data/stride.db \

--artifacts ./data/artifacts

Your next site is one command away

Install Stride, open the admin, and publish a page in the time it takes to read the WordPress system requirements.

$ npm install -g @guuslab/stride