Smart Project Groups: Zero-Config Microservices on Launchverse

By default, every project you deploy on Launchverse operates as an isolated island. But modern applications rarely live alone—your Next.js frontend needs to talk to your Go API, and your Go API needs to connect to a Postgres database.

Instead of dealing with complex firewall rules or exposing your databases to the public internet, Launchverse provides Smart Project Groups.

Smart Groups transform your isolated projects into a cohesive, secure ecosystem with two massive benefits: Zero-Config Internal Networking and Automated Secret Injection.

1. Zero-Config Internal Networking

When you add applications and databases to a Smart Group, the Launchverse Engine automatically wires them together on a private, isolated network.

Every resource in the group is assigned a clean, predictable internal DNS name based on its project name.

How it works:

If you deploy a Postgres database named Finance DB and a Go API named Finance API into a group:

• Launchverse cleans up the names and assigns internal network aliases: FinanceDB and FinanceAPI.
• Your API can now connect to your database using the connection string: postgres://user:pass@FinanceDB:5432/db.
• Your frontend can securely fetch data from your API internally via http://FinanceAPI:8080.

The Benefits:

• Speed: Traffic never leaves the server. It is significantly faster than routing over the public internet.
• Security: You do not need to expose your database ports to the outside world. They remain locked down and only accessible to other apps within the same Smart Group.

2. Automated Secret Injection

Managing environment variables across a microservice architecture can be tedious. If five different workers all need the same REDIS_URL or STRIPE_SECRET_KEY, updating them manually one-by-one is a recipe for broken deployments.

Smart Groups solve this with Shared Environment Variables.

How it works:

1. Navigate to your Group's dashboard page.
2. Define an environment variable at the Group Level (e.g., INTERNAL_API_URL=http://FinanceAPI:8080).
3. Launchverse will automatically inject that variable into every single application within the group.

If a group variable shares the same name as a local variable you defined directly on a specific app, the group variable wins. This guarantees that your group acts as the ultimate source of truth for shared secrets, keeping your entire stack perfectly in sync.

3. Dependency-Aware Deployments

When managing a stack of connected services, deployment order matters. If your frontend boots up before your database is ready to accept connections, your app will crash.

Launchverse handles this orchestration for you automatically.

When you click Deploy Group from the dashboard, the Engine performs a coordinated rollout:

1. Network & Secrets Sync: All network aliases and shared variables are applied to the Engine.
2. Database First: All databases in the group are restarted.
3. Health Checks: Launchverse pauses and polls the Engine, waiting until every database reports a running and healthy state.
4. App Rollout: Only after the databases are ready does Launchverse trigger the deployment of your downstream applications.

Getting Started

To create your first ecosystem:

1. Go to the Groups tab in your Launchverse dashboard.
2. Click Create Group and give it a name (e.g., "Production Web Stack").
3. Use the dropdowns to add your existing applications and databases to the group.
4. Define any shared Environment Variables you want distributed across the group.
5. Click Deploy Group to apply the configuration and rollout your stack!

You can also visit the Canvas tab of any project in a group to see a visual map of your newly connected microservices architecture.