Service Groups
Keep services that belong together in one group.
A service group is a labelled box around services that belong together. It has a name, an icon and a description, and it keeps an environment readable once it holds more than a handful of services.
Where groups come from
Deploying a template creates a group with all of the template's services inside. Supabase arrives as one group of nine services, not nine loose cards.
Creating a group by hand, or moving services in and out of one, is not in the UI yet. Both are available through the API and the MCP server.
Ordering
The services page searches and sorts the same way as the projects page. Searching for a group's name shows the whole group.
On Custom, drag a group to move it with all of its services, or drag a service inside a group to reorder the group. Services stay in their group while you drag: one dropped outside its group goes back where it was. The order is shared by everyone who can see the environment, and changing it needs the editor role. New services and groups go to the top, and a service added to a group goes to the top of that group.
Through the API, list-service takes the same sort_by and sort_order as list-projects. reorder-services orders the groups and the services outside them, and reorder-service-group orders the services inside one group.
Rename
Open the menu on the group and choose Rename to change its name and description.
Delete
Delete on a group deletes every service inside it. This cannot be undone.
The volumes of those services are kept. They stay in the environment, unmounted, until you delete them or mount them somewhere else.
Deleting the last service of a group removes the group as well.
Template settings
A group that came from a template remembers what you filled in when you deployed it. Domains, storage sizes and other visible inputs can be changed later through the API, and the template updates every setting that depends on them. Storage can only grow.