Push. Ogschaut. Then live.

GitHub deployment for your team: share a preview, review the changes together, then publish the approved image without rebuilding.

For Next.js, Node, static sites and Docker projects.

Create your first preview Understand the workflow
  • Separate environments
  • Release without rebuilding
  • Traceable releases

bergwerk/kundenportal

Product view · example data

Preview · PR #184

Release for feature/customer-export

a81fc2d · Add encrypted export archive

Preview ready
  1. 1

    GitHub event verified

    Repository and commit are bound to the installation

    Received
  2. 2

    Deployment queued

    Preview and production settings stay separate

    Recorded
  3. 3

    Artifact built

    Immutable image stored for this release

    Ready
  4. 4

    Preview published

    kundenportal-pr-184.preview.ogschaut.de

    Open

Example data, real product path: signed GitHub event, isolated build, immutable image and routed preview.

GitHub deployment, from push to approval

Send your team a preview link before the change goes live. Once it is approved, publish that exact image with your production settings.

  1. 1

    Connect the repository

    Choose which repositories ogschaut can access through your GitHub App installation.

  2. 2

    Build a preview

    Your first push creates a preview with its own URL. Each pull request can have its own environment.

  3. 3

    Review together

    Open the preview from your pull request. Check the changes with your team, with status and logs close at hand.

  4. 4

    Publish the approved image

    Publish the reviewed image with production variables. After your first release, default-branch pushes can update production automatically.

A clear path from GitHub to production

Keep the repository, previews, logs and release history in one project. Your team can see which version is ready and what goes live.

A preview your team can open

Share a preview URL from the pull request. Each preview runs independently, so reviewing one change does not replace another.

The image you reviewed

Build once, then release the same image. Production uses its own variables, without a second source build that could change the result.

Ready before it goes live

Production traffic switches after the new application is ready. Previous production images remain available for rollback without rebuilding.

How GitHub deployment works Compare the Vercel alternative

Start small. Grow with your projects.

Compare projects, team seats and included usage before choosing a plan. Build, runtime and log retention limits are listed up front.

Pro

For solo developers who ship real projects.

$29.00 / month

Choose plan

$24.16 / month (paid yearly)

Choose plan
  • 10 projects
  • 3 team members
  • 1,000 build minutes per month
  • 500 runtime GB-hours per month
  • 7 days of log retention

Team

Most Popular ✨

For teams that deploy together every day.

$99.00 / month

Choose plan

$82.50 / month (paid yearly)

Choose plan
  • 50 projects
  • 10 team members
  • 5,000 build minutes per month
  • 3 concurrent builds
  • 30 days of log retention

Business

For organisations running production workloads at scale.

$299.00 / month

Choose plan

$249.16 / month (paid yearly)

Choose plan
  • 200 projects
  • 25 team members
  • 20,000 build minutes per month
  • 10 concurrent builds
  • 90 days of log retention

Questions before your first deployment

GitHub deployment, supported projects and your first production release.

What happens after a GitHub push? Your first pushes create previews with their own URL. You choose when to release a reviewed image. After the first production release, pushes to the default branch can update production automatically.
Is ogschaut a Vercel alternative? ogschaut is an alternative for teams that need GitHub previews and controlled production releases for container-based applications. Custom domains and provider-specific edge functions are not part of the current release.
Which projects can I deploy? Deploy GitHub repositories with a Dockerfile, Next.js, Node or a static site. Nuxt, SvelteKit and Astro need a production start command that serves the application on port 8080.
How does rollback work? A rollback reuses the image of an earlier successful production release. The source code is not rebuilt, and traffic switches only after the restored application is ready. Current production variables still apply.
What does ogschaut mean? It is Franconian for having had a look. That is the idea: inspect your preview before you publish it.

Ready to ogschau your next release?

Connect your GitHub repository and give your team a preview to review.

Create organisation