Back to ogschaut

Vercel alternative for DACH

A Vercel alternative when preview workflow and controlled runtime both matter

ogschaut is a practical Vercel alternative for DACH teams that want GitHub previews and calm production promotion while keeping a transparent path to platform operation in Germany. It focuses on the release workflow, not global edge feature parity.

Import a repository See the deployment path

What ogschaut deliberately optimises

Review workflow
Signed GitHub event, independent preview URL, status and logs on one ordered deployment
Whether preview and production use the same approved artifact
Artifact integrity
Content-addressed image digest; production promotion and rollback do not rebuild source
Whether a promotion can trigger a different build result
Runtime boundary
Provider-neutral Kubernetes runtime agent with namespace, secret and resource boundaries
Where workloads, logs, telemetry and backups are processed
Initial framework scope
Dockerfile, Node, Next.js and static, plus adapters with a production start command
Whether proprietary edge, image or function features are migration blockers
Release recovery
Readiness-gated traffic switch and rollback to a stored immutable image
How quickly the previous known artifact can be restored

A good fit

  • DACH agencies sharing pull-request previews with clients
  • B2B SaaS teams that need an explicit build and runtime boundary
  • Node, Next.js, static or Docker workloads that can serve on port 8080
  • Teams that value immutable promotion and rollback over proprietary edge features

Not feature parity

Choose another platform if your application depends on proprietary edge middleware, a global edge-function runtime, managed image optimisation or a provider-specific data product. ogschaut does not present those as available.

The migration boundary is a standards-based container image and a normal HTTP service, which keeps the supported path explicit.

Questions about switching

Is ogschaut an open-source Vercel clone? No. It is a focused deployment product built on a Phoenix control plane, BuildKit and Kubernetes. It implements its own provider-neutral release contracts.
Can I migrate a Next.js application? Yes when the application builds and starts as a normal Node service on port 8080. Audit proprietary edge, image, analytics and data integrations separately.
Does ogschaut promise a global edge network? No. The product focuses on a transparent DACH release and runtime path. It does not claim global edge parity.

Test the path with a real repository

Import GitHub, publish a preview and promote the exact reviewed image to production.

Create organisation