Start a new service on the paved road by default
Repository, CI/CD, tests and catalog entry created together from a maintained template.
“I need a new repo for the notifications service — and can someone remind me which pipeline file we are standardising on now?”
What the wait costs
The CI config gets copied from a two-year-old repo, along with the deprecated base image and the secret nobody meant to keep.
Copying the last service is how drift starts: the base image, the pipeline and the lint rules all freeze at whatever the source repository knew. App Builder generates from a template the platform team maintains, so a service created today carries today’s standards. Over fifteen templates cover React, Vue, Angular, Express and FastAPI, and each one produces a repository that is already registered in the catalog with an owner.
How it works
- 01Choose a template and answer the setup wizard — name, owner, repository.
- 02Fenwave creates the Git repository and applies the right permissions.
- 03CI/CD, linting and a test scaffold land in the first commit.
- 04The service is registered in the catalog with its owner already set.
- 05Push, and the branch environment workflow applies from day one.