Deploy reusable infrastructure with a plan you can review.
Configure reusable infrastructure templates, deploy them to your cloud account, and ask Mica to inspect environments and preview deployments. For developers shipping an app and platform teams standardizing delivery.
- Demo project
- Staging
- Add infrastructure
Sample infrastructure flow for the Amazon S3 template in Staging. The settings step shows the bucket name, versioning, public access, a reference to another component's output and an optional expiry. The review step lists the name, template, version and settings, offers to add and deploy now, and explains what happens next.
Infrastructure delivery
What you get
A configured infrastructure component, with its deployment status and logs in the same workspace.
What you bring
- A Microtica project, a template that fits your workload, and access to connect the target cloud account.
- AWS setup requires permission to create the connection CloudFormation stack.
How it works
Know what happens before you start.
- 01
Choose a building block
Select an infrastructure template and version for your environment. Review required inputs and references to other resources.
- 02
Check the configuration
Set the component name and inputs. Choose to add it for later or add and deploy it now. The review screen lists what will happen.
- 03
Follow the deployment
Start the deployment to the environment’s cloud account, then follow its status and logs. Use Mica to inspect the environment and preview subsequent deployments.
Reusable infrastructure
Microtica components package infrastructure and inputs for reuse. Custom components can use CloudFormation or Terraform through a Microtica pipeline.
Linked components
A setting can take another component’s output, such as a bucket name, so the components in an environment stay connected.
With Mica
Ask Mica to keep it running and current.
Once infrastructure is in an environment, Mica can check it, show what a deploy would change and prepare the deploy. Nothing runs until you approve it.
How approvals work- Read an environment’s resources, their settings and its health
- Preview a deploy before anything changes
- Redeploy an environment’s infrastructure
- Find newer component versions and deploy them
“Microtica provided us with excellent guidance and support throughout the migration process, and the cloud platform has been a breeze to use since then. We are very thankful for the cost savings measures the platform provides.”
Access and control
A cloud connection can make changes
AWS integration uses an IAM role and temporary STS credentials. Provisioning is a write operation. Review the connection permissions before granting access, and review the target environment before deploying.
Try it on one service.
Start free with a development project, or bring your setup to a demo.