Platform / Application Hosting
Deploy static sites and supported server applications from GitHub. RustaBase manages releases, previews, build configuration, domains, and monitoring while source builds remain in your repository workflow.
Application delivery
Your repository builds the application. RustaBase receives the release, checks its health and delivers it through a managed HTTPS address.
Choose the repository, production branch and build settings.
GitHub Actions installs dependencies and produces the published output.
The new copy must become healthy before visitors switch to it.
Serve through HTTPS, inspect traffic and keep a recovery path.
Application delivery
Connect your repository, configure the build and runtime, review changes, and operate releases from one application page.
Keep your code, build workflow and build history in your own repository. RustaBase manages the release that visitors use.
Start with the closest framework preset, then align the settings with your repository. Package static output or a supported server application's built output.
Review an eligible change on its own address before merging. New commits update the preview for the same pull request.
Manage configuration outside source code and choose whether a value belongs to production, previews or both.
Give your application a managed address and connect verified custom domains when your plan includes them.
Follow the source commit, build status and release result. Switch to a retained successful release when you need to recover.
Control unwanted visitor traffic at the RustaBase edge before it reaches your running application.
Connect a release's behavior to its traffic and resource usage. Investigate requests and build failures from the application page.
Start from a template without giving up control of its source. The application is copied into your own GitHub repository.
Let a CMS or trusted automation trigger the same redeploy action as the console. Treat the generated hook address as a credential.
Before the first deployment
Match the application settings to the repository rather than guessing from a framework name. The published folder must contain the static files or supported server output needed to run your application.
Check the build settings guideApplication Hosting delivers the experience visitors open. Backend Engine provides PostgreSQL, users, files, APIs and realtime. Connect them through the Project's API address and access rules; use either service independently when that fits your product.
Switching to a previous application release does not undo external database writes or migrations. Keep changes compatible with your recovery plan, and manage backend backups separately.
In your own GitHub Actions workflow. RustaBase receives the packaged result and manages the running release and delivery. Configure any test step you need in the workflow; a successful build is not a substitute for your application's tests.
Supported server presets package GitHub-built output onto a Node or Bun runtime. Select a compatible framework adapter, published folder and start command; a framework name alone does not guarantee every deployment mode works. Static sites can use export or prerendering instead.
Previews apply to eligible same-repository pull requests into the production branch and are subject to plan limits. Fork pull requests are excluded to avoid exposing deployment credentials. Closing or merging the pull request removes its preview.
The current release remains in place rather than switching visitors to an unhealthy new copy. Review deployment status and build failure details before trying again.
Only a release that is still retained and runnable is eligible. Older deployment history may remain visible after its release has been retired. Check eligibility in Deployments before relying on rollback.
Availability and limits depend on your workspace and application plan. Check pricing and the application's available settings before choosing your production setup.
How it works
A production-branch release uses the live deployment path. Pull requests use restricted preview credentials and never publish over production.
Your repository remains the source of code, settings, and build history.
GitHub Actions installs dependencies, builds the output, and reports each step.
RustaBase keeps the current release available while the next one becomes ready.
Check health and usage, or return to the previous kept release when needed.
One workspace, every layer
Start free and add the platform capabilities your product needs as it grows.