W7S

W7S is an open source deployment platform managed directly from GitHub Actions workflows. The core currently powers W7S.cloud and can also be self-hosted.

The core idea is simple:

1. Put an app in a GitHub repository.
2. Add the W7S GitHub Action.
3. Push to GitHub.
4. W7S verifies the GitHub Actions OIDC token, receives the deploy archive, and serves the app.

Minimal workflow

name: Deploy

on:
  push:
    branches:
      - main
  workflow_dispatch:

permissions:
  id-token: write
  contents: read

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5

      - uses: w7s-io/w7s-cloud@v1

What W7S can deploy

• Static frontends built into dist/, dist/client/, build/, out/, or frontend/dist/.
  • w7s-io/example-static-site
• Native backend code from backend/ or worker/, authored or built as JavaScript or TypeScript runtime modules.
  • w7s-io/example-native-backend
• Fullstack apps that include both a JavaScript/TypeScript backend root and a static frontend root.
  • w7s-io/example-fullstack-ts
• Stateful object bindings for JavaScript/TypeScript native backends.
  • w7s-io/example-durable-counter
• Serverless DBs for JavaScript/TypeScript native backends.
  • w7s-io/example-serverless-database
• Postgres bindings for external databases.
  • w7s-io/example-postgres-binding
• W7S-provided AI service bindings for JavaScript/TypeScript native backends.
  • w7s-io/example-ai-joke
• Backend-to-backend RPC through internal service bindings.
  • w7s-io/example-rpc-client
  • w7s-io/example-rpc-datetime
• Background queues delivered to JavaScript/TypeScript native backends.
  • w7s-io/example-queue-worker
  • w7s-io/example-queue-producer
  • w7s-io/example-queue-consumer
• Cron schedules delivered to JavaScript/TypeScript native backends.
  • w7s-io/example-schedules
• Durable workflow instances delivered to JavaScript/TypeScript native backends.
  • w7s-io/example-workflows
• Daily usage rollups, hourly platform usage sync, app suspension, warning thresholds, and daily limits.
  • w7s-io/example-usage-check
• Platform event analytics exposed through an authenticated API.
  • w7s-io/example-logs
• Backend console and exception logs exposed through an authenticated API.
  • w7s-io/example-logs
• Read-only agent-facing infrastructure inspection for deployments, routes, resources, observability links, and safe next actions.
  • Agent API
• Custom domains declared with a CNAME file.
  • w7s-io/example-fullstack-ts

Note:

This documentation is also an example, deployed from github using a Github Actions workflow.

W7S vs Others

Feature	W7S	Vercel	Cloudflare Pages + Workers	Railway / Fly.io
GitHub-native deployment	Yes (one Action)	Good	Manual	Good
Open Source + Self-hostable	Yes	No	Partial	No
Native JS/TS Backends	Yes	Serverless Functions	Workers	Yes
Serverless DB	Included	Add-on	Native DB	External
External Postgres	Supported	Yes (paid)	Manual	Yes
Queues, Cron & Workflows	Native	Limited	Yes	Yes
Vendor Lock-in	None	High	Medium	High
Pricing	Free self-host + hosted	Usage-based	Usage-based	Usage-based

Continue with Deploy From GitHub, then add the daily quota check recommendation.

To run your own W7S cloud on a Cloudflare account and domain you control, see Self Host W7S.