# bhvr

> A stack made for the open web

## Docs

- [Get started](/getting-started): bhvr is a framework used to build apps that are not tied down to a single provider, and each piece can be deployed in multiple places.
- [Why bhvr?](/why-bhvr): I get it. Why another typescript framework for web apps? Aren't we just heaping fuel to the already massive dumpster fire?
- [Cloudflare Workers](/deployment/server/cloudflare-workers): One of the simplest ways to deploy your `server` is through Cloudflare Workers, which are lightweight, fast, and very inexpensive.
- [Railway](/deployment/server/railway): For a simple Bun server deployment you can use Railway by changing just a few lines of code.
- [Cloudflare Pages](/deployment/client/cloudflare-pages): A great way to host your bhvr client, especially since your server can be hosted with Cloudflare Workers. There are two primary ways you can host your client through Pages:
- [GitHub Pages](/deployment/client/github-pages): Since the bhvr client is a simple static site you can deploy it just about anywhere, including GitHub Pages. Just follow these steps:
- [Netlify](/deployment/client/netlify): One of the classic static site providers still gives developers a great experience for deploying sites, including your bhvr client! There are multiple ways you can deploy your client package to Netlify:
- [Cloudflare](/deployment/single-origin/cloudflare): By using Cloudflare Workers you can host the `server` and the `client` in one deployment thanks to the built in [Static Assets Feature](https://hono.dev/docs/getting-started/cloudflare-workers#serve-static-files). With this approach everything will come through a single origin where any routes not covered by Hono will fallback to resolving via the static assets folder, which in our case is our React app.
- [VPS / Docker](/deployment/single-origin/vps-docker): Serve both your frontend and API from the same process, same port, and same origin—ideal for fullstack apps where simplicity matters.