Connect the repository.
Import it from GitHub or GitLab and choose the branch that should go live.
Angular hosting
Angular hosting.
Deploy an Angular app from GitHub or GitLab. Lahyer reads angular.json, runs your build and serves the browser output from a global edge with HTTPS, so routes and deep links keep working.
Deploy your projectangular.jsonOutput path read for you
Deep linksUnknown paths serve index.html
PreviewsA URL for every pull request
What Lahyer does with it
How Angular builds and runs.
Lahyer fills these in from your repository. Change anything that does not fit in the project's build settings.
| Detected from | @angular/core in your package.json dependencies |
|---|---|
| Install | npm, pnpm, Yarn or Bun, chosen from your packageManager field or lockfile |
| Build | Your build script, or ng build |
| Output | The browser folder from angular.json, for example dist/<project>/browser/ |
| Server-side rendering | Not run as a server yet: Lahyer serves the browser build |
Your first deploy
Three steps
to a live URL.
Check the output path.
Lahyer reads the build target in angular.json. The application builder in Angular 17 and later writes to a browser/ folder, which Lahyer picks up.
Push and ship.
Every push deploys, and every pull request gets a preview URL to review before you merge.
A few useful answers
Before you begin.
Does Angular server-side rendering work?
Not as a server yet. When server-side rendering is configured, Lahyer serves the browser build as a static site. If you need a server today, deploy the app with a Dockerfile.
Which Angular versions work?
Lahyer reads angular.json for the application builder in Angular 17 and later, and for the older browser builder.
Will an Angular app sleep on the free plan?
No. Static files are served without a running server, so there is no cold start on any plan.