# W7S

> W7S is an open source deploy platform for GitHub-native apps. GitHub Actions builds the app, the W7S deploy action uploads the deploy output, and W7S serves it from hosted or self-hosted infrastructure.

W7S is for static frontends, JavaScript/TypeScript native backends, and fullstack apps that should deploy directly from a repository workflow. W7S Cloud deploys can use the repository GITHUB_TOKEN instead of a separate W7S account, card, dashboard, or cloud setup. The deployment workflow is the control plane.

Important notes:
- Hosted W7S Cloud deploys use the `w7s-io/w7s-cloud@v1` GitHub Action.
- Public hosted app URLs use `https://<github-owner>.w7s.cloud/<repo-name>`.
- Custom domains are declared with a `CNAME` file and DNS pointing at W7S.
- The same open source core can be self-hosted.

## Docs

- [W7S documentation index](https://w7s.io/docs/llms.txt): Agent-friendly index of the W7S docs.
- [Full W7S docs context](https://w7s.io/docs/llms-full.txt): Full Markdown documentation context generated from the docs source.
- [Getting started](https://w7s.io/docs/): Minimal GitHub Actions workflow and overview of supported app types.
- [Deploy from GitHub](https://w7s.io/docs/deploy-from-github/): Configure repository workflows for W7S deploys.
- [Self host W7S](https://w7s.io/docs/self-host/): Run your own W7S deployment cloud.
- [Custom domains](https://w7s.io/docs/custom-domains/): Configure app domains with CNAME files and DNS.

## Key Resources

- [W7S Core](https://github.com/w7s-io/w7s-core): Open source deployment runtime and management plane.
- [W7S Cloud GitHub Action](https://github.com/w7s-io/w7s-cloud): GitHub Action used for hosted W7S deploys.
- [Example fullstack TypeScript app](https://github.com/w7s-io/example-fullstack-ts): Example repository for a frontend plus native backend.
- [Nodepad demo starter](https://github.com/guerrerocarlos/nodepad): Starter app referenced by the landing page quickstart.

## Optional

- [AI Website Builder: Turn an AI-Generated Site Into a Real Website](https://w7s.io/blog/ai-website-builder-to-real-website/): AI website builders can generate the first draft. The next step is owning the code, putting it in GitHub, deploying it repeatably, and attaching the real-world pieces a business site needs.
- [Best AI Website Builder for People Who Want to Own the Code](https://w7s.io/blog/best-ai-website-builder-own-the-code/): The best AI website builder depends on whether you want a hosted builder, a cloud IDE, an AI editor, or a repo-first workflow that can deploy from GitHub.
- [Free AI Website Builder vs Free Hosting: What Actually Stays Free?](https://w7s.io/blog/free-ai-website-builder-vs-free-hosting/): Free AI website builders can create a prototype quickly, but hosting, domains, exports, forms, databases, and future changes decide what the site really costs.
- [How to Build a Website With AI and Deploy It From GitHub](https://w7s.io/blog/build-a-website-with-ai-and-deploy-from-github/): A practical workflow for using AI to create a website, putting the files in GitHub, and deploying the result with W7S.
- [Create a Website With AI Without a Website Builder Subscription](https://w7s.io/blog/create-website-with-ai-without-builder-subscription/): Use AI to generate the website, GitHub to own it, and W7S to deploy it without turning the first draft into a permanent website-builder subscription.
- [Netlify Drop Is Easy. GitHub First Is Still Worth It.](https://w7s.io/blog/netlify-drop-vs-github-first-deploys/): Netlify Drop is a fast way to publish a folder, but putting the project in GitHub first gives beginners a repeatable path to W7S deploys, history, rollbacks, and reviewable changes.
- [GitHub Basics for Your First W7S Deploy](https://w7s.io/blog/github-basics-for-first-w7s-deploy/): A beginner-friendly path from no GitHub experience to a repository that can deploy with W7S.
- [From Empty Folder to W7S Deploy](https://w7s.io/blog/from-empty-folder-to-w7s/): Start from scratch with a tiny website, put it in GitHub, and deploy it to W7S with GitHub Actions.