Status
Whether website, online shop, agency project or SaaS — the right solution for every project on one platform.
Explore solutions
Stack not listed? Any OCI image and any language can be run directly as a container.
Deploy your own images

Deploy the moment
you push.

Connect a Git repository and the LAY7 cloud detects your stack, builds an image and switches the new version live – in four traceable phases and without a Dockerfile.

my.lay7.cloud
Live deployment of an application in the LAY7 cloud with four completed phases from "Code fetched" to "Live"
From push to live Code · Build · Image · Activation
storefront live
main · auto-deploys on push
Production · 2 replicas
Git push
triggers build and deployment automatically
4 phases
per deployment, tracked live
0 s
downtime – activated only after the health check
100% DE
data centers in Germany, GDPR compliant
On every deployment

Four phases,
fully automatic.

Every deployment takes the same path – visible in real time, from the fetched commit to the active version. Trigger it with a click or leave it to a push.

No hidden scripting, no black box: every step is named and traceable.

Code fetched

The chosen commit is fetched from your repository – exactly the state you're deploying.

Application built

Language and framework are detected, dependencies installed, an image is built – without a Dockerfile.

Image published

The finished image lands in a project-specific registry, versioned and reusable.

Live

The new version starts, passes the health check and takes over traffic – without interruption.

Overview

Every environment
at a glance.

For each environment you see the currently active deployment and the latest releases – with commit, trigger and timestamp. A new build is never more than a click away.

Production listens on main and deploys automatically on every push. Staging and preview are tied to their own branches and stay cleanly separated.

Overview of a production environment in the LAY7 cloud with an active deployment and the latest releases
Stacks & frameworks

Detected and
built to match.

The platform reads your project and decides on its own how to build and start it. Wherever you want more control, every setting is exposed – from the language version to additional system packages.

For Laravel, the path is especially short: typical building blocks are available as presets and active with a single click.

  • Octane, Horizon, Reverb, Pulse and Inertia SSR are available as presets – enable them per environment instead of setting them up yourself.
  • JavaScript and TypeScript projects are detected, built and started with the matching runtime.
  • You set the language version and additional extensions per environment – fully managed and kept up to date.
  • The platform builds a generic project too; you then define the build and start command yourself.
  • Migrations run before the switch-over. If a step fails, the active version stays untouched.
Processes

More than just
the web process.

Alongside your app, you run long-lived processes – a queue worker, Horizon, a WebSocket server or SSR. Each process gets its own compute.

For Laravel, a single click is enough: Horizon, Reverb or Inertia SSR are available as presets and start with the right command.

Processes view of an application in the LAY7 cloud with a Horizon worker and a Reverb WebSocket service
Tasks

Scheduled tasks,
to the minute.

Schedule recurring commands as tasks with a schedule and timezone – from the Laravel scheduler running every minute to a nightly cleanup.

Every task shows its schedule and the status of its last run, with its own logs to review.

Tasks view of an application in the LAY7 cloud with the Laravel scheduler running every minute
Resources & variables

Connect services,
manage values.

Attach a database or cache directly to the environment. The credentials land automatically as environment variables in your app – in the format your framework expects.

Databases & caches

Connect MariaDB, Redis or Valkey directly from the environment – no copying hosts and passwords by hand.

Automatically linked

A connected service writes its credentials into the app as variables – ready to use immediately.

Variables & secrets

Manage values centrally per environment. Mark anything sensitive as a secret so it stays masked.

Build vs. runtime

Separate what's only needed while building from what the running app actually sees.

The right fit

Applications, Spaces
or Container?

Applications are built for your own code from a repository: you push, the LAY7 cloud builds and runs it. Ideal when a framework like Laravel or a Node.js stack is involved.

If you'd rather work classically over SSH and SFTP, or install an app with a click, Spaces is the right choice. If you bring a finished image or want to combine multiple containers into one stack, Container Hosting gets you there.

All three share the same infrastructure, the same management and the same invoice – you decide per project, not per provider.

More from the platform

An app rarely
comes alone.

Web space, your own containers and managed databases fit together seamlessly – one dashboard, one invoice.

Get started

From commit
to live app.

Connect a repository, trigger the first build, see the result live – with guaranteed performance and full cost control. No credit card required.

  • Build without a Dockerfile
  • Dedicated environment per branch
  • Roll back anytime