Magalu Cloud

Orkestia ships a first-class Magalu Cloud port: the mgc.* family (~90 workflows) covers compute instances, managed Kubernetes, DBaaS, load balancers, networking (VPCs, subnets, security groups), block and object storage, container registry, and SSH key management. For teams building on Brazilian infrastructure this is a full alternative compute target, not a token integration.

What the grant is

A Magalu connection is an API key issued in your Magalu Cloud account. Orkestia acts with that key's permissions; rotating or revoking the key in your Magalu console cuts access instantly. As with every provider, the key is stored as an org-scoped connection and never appears in workflow inputs.

Setting it up

1. Read the prerequisites for the mgc.* family you're targeting via get_workflow_prerequisites or the dashboard connection flow.
2. Issue a dedicated API key in your Magalu account (one per environment, not your personal key).
3. Create the org-scoped connection; validation runs a read-only check (e.g. listing regions) before it's usable.

What people run on it

• Managed Kubernetes — mgc.kubernetes.* for cluster lifecycle, then the cloud-agnostic kubernetes.* family for in-cluster work.
• Databases + load balancing — mgc.dbaas.*, mgc.lbaas.*.
• Networking — mgc.network.* (~22 workflows) for VPC-level topology.
• Storage + registry — mgc.object_storage.*, mgc.block_storage.*, mgc.registry.*.
• Runner capacity — runners provisioned on Magalu consume this connection.

Browse the full family at reference.orkestia.dev/mgc.