Open source GitHub-native deploys

The Cloud that just works.

w7s.cloud is the hosted W7S deploy environment. GitHub Actions builds your app; W7S ships the output to live environments and serves it at a public URL. Your deployment workflow is the control plane.

Deploy from GitHub Read the docs

W7S Cloud hosted

No account needed

Repo owned deploys

Deploy target

Nothing is deployed here yet.

Nothing is deployed at https://w7s-io.w7s.cloud/static/css/main.d8fdd586.css yet.

W7S uses one subdomain per GitHub owner: w7s-io.w7s.cloud. The same-name repo uses the root path, and every other repo deploys under /repo-name/ on that same subdomain.

To deploy to this domain and path, use w7s-io/static.

After it deploys, W7S will serve it at https://w7s-io.w7s.cloud/static/.

.github/workflows/deploy.yml

name: Deploy

on:
  push:
    branches:
      - main
  workflow_dispatch:
  schedule:
    - cron: "17 9 * * *"

permissions:
  contents: read
  issues: write

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
        if: github.event_name != 'schedule'

      - uses: w7s-io/w7s-cloud@v1
        with:
          token: ${{ github.token }}
          usage-check-only: ${{ github.event_name == 'schedule' }}

Add this GitHub Actions workflow to any repo and push to GitHub. Manual runs deploy too; scheduled runs only check usage limits and update the warning issue. W7S verifies access with the repo's GitHub token and serves it at <owner>.w7s.cloud/<repo>/.

No dashboard required

Deploys start from GitHub Actions, so repository permissions and workflow history remain the source of truth.

Frontend and backend

Ship static apps, JavaScript or TypeScript native backends, queues, schedules, workflows, storage, and custom domains.

Usage-aware by default

W7S tracks usage and reports quota pressure back to the repository through the deploy workflow.