Bring your build tool
Use Vite, a static site generator, or a framework configured for static export. Set the build command and the directory that contains the finished site.
Static sites
Build your frontend.
Publish your work.
Put portfolios, content sites and frontend applications online from Git. Openstead builds your project, publishes its static files and connects your custom domain.
Your code. Infrastructure included.
YOUR BUILD OUTPUTdist/├── index.html├── style.css└── assets/app.js
a little corner of the web
a.WORK ABOUT
Ideas deserve
to be seen.Designed. Built. Published.
to be seen.Designed. Built. Published.
Static filesHTML, CSS, JavaScript and assets
Git buildsPublish from your repository
Free hostingWithin included usage allowances
STATIC SITES ON OPENSTEAD
Everything your frontend needs. Nothing it has to run.
When your project produces static files, publish those files directly. There is no application process to start or server runtime to maintain.
Publish from a connected branch
Keep source code in GitHub and releases in your deployment history. Review build output when a dependency or configuration needs attention.
Finish with your own domain
Attach a custom domain and configure the DNS records shown in the console. HTTPS certificates are managed for verified domains.
MADE FOR YOUR STACK
A small deployment surface. A familiar build.
Build the same project you run locally and publish its generated directory. Single-page applications can use route fallback, while content sites can provide their own 404 page.
- A static service has no application container or shell.
- Build-time variables are available to your build command.
- Keep private credentials in a backend, never in a browser bundle.
Vite applicationopenstead / configuration
STATIC SITE CONFIGURATIONRepository your-team / storefront
Branch main
Build command npm ci && npm run build
Publish directory dist
dist/
index.html
assets/
app.js
app.cssFor Next.js, use a static export and the generated output directory. Server-rendered Next.js belongs on a web service.
PUT IT TO WORK
Built for the work
your application does.
Portfolios and company sites
A clear home for your work, your business and the people you want to reach.
Frontend applications
Static React, Vue or Svelte builds that talk to an API hosted on Openstead or elsewhere.
Content and reference sites
Publish generated articles, product information and knowledge bases without running a backend.
HOW IT WORKS
Source code in. A website out.
Select the project
Connect your repository and branch, then choose the app directory if the code lives inside a monorepo.
Set the output
Confirm the build command and publish directory. The directory must contain the HTML and assets you want visitors to receive.
Publish and connect
Deploy the generated files, test the platform URL, and attach your domain when you are ready to share.
Can a static site run server-side code?
Static sites serve generated files. Use a web service for server-side rendering, API routes, PHP execution or any code that must run for each incoming request.
Does Openstead support single-page applications?
Yes. Static deployments support a single-page application fallback so client-side routes can load the application entry point. Check deep links as part of your deployment.
Can I connect my own domain?
Yes. Add the domain to your static service and use the required DNS records. The console shows verification and certificate status.
Are environment variables private on a static site?
Variables are provided to the build, but anything your build includes in JavaScript or other public files is visible to visitors. Use a backend service for private keys and credentials.
MAKE YOUR NEXT MOVE
Put your work where people can find it.
Your code. Infrastructure included.