Start free

Microtica Platform

Ship your apps to your own cloud.

Paste a repository and your app is live in your own cloud account, with a deploy on every push. Run it as containers, on Kubernetes, serverless or as a static site, add infrastructure from templates, and ship releases across environments. Mica, its AI assistant, does the setup with you and asks before it changes anything.

Start freeBook a demo

  1. Your repository

    Your code

    • GitHub
    • GitLab
    • Bitbucket

  2. Microtica

    The delivery workflow

    • Zero-config builds
    • Releases
    • Infrastructure as code
    • AI investigation
    • AWS cost management

  3. Your infrastructure

    Your cloud

    • Containers (Amazon ECS)
    • Kubernetes
    • Serverless and static sites
    • AWS, GCP or Exoscale

A workflow overview. Available templates and actions depend on your provider and environment.

Follow one release

A deployment you can follow.

Review the source revision and target environment, then follow build and deployment progress. Logs and deployment history stay connected to the service.

A push to main runs the pipeline: build, test, then deploy to Staging. Each step keeps its status and logs.

  1. Demo project
  2. catalog-service
  3. Pipeline run
Sample data

What your team can do

The work around each release.

Use templates or your own components. Keep infrastructure, delivery and operations connected to the environments your team runs.

Make infrastructure repeatable

Deploy Terraform or CloudFormation components. Configure their inputs for each environment and follow deployment progress.

Explore infrastructure delivery

Go from repository to a live app

Paste a repository and approve one plan. The app goes live in your own cloud account, and every push deploys.

See how it works

Ship releases

Build several apps and components from a branch or tag, or promote staging to production, as one release with one approval.

Explore releases

One page for each app

Visit, logs, events, deploys and settings on one page, wherever the app runs. Remove it when you are done.

Explore monitoring

Ask why a deployment failed

Investigate with deployment history, logs and resource context. Review an approval card when Mica proposes a deployment or scaling action.

Explore AI investigation

See spending and schedule downtime

Review AWS cost reports and configure saving schedules for supported non-production AWS resources.

Explore AWS cost management

Fit with your stack

Start with what you already have.

Importing application code and adopting an existing cloud estate take different steps. Choose the path that matches your setup.

Your starting pointHow Microtica fitsNext step
A Git repositoryConnect GitHub, GitLab or Bitbucket. Run it as containers with no cluster to manage (Amazon ECS), on Kubernetes, or start from a serverless or static-site template.See where it can run
Existing Kubernetes clusterConnect its API endpoint and service account so Microtica can deploy applications to it. The cluster can run in your cloud or on-premise.See cluster requirements
New infrastructureConnect AWS, GCP, or Exoscale and choose a compatible template or infrastructure component. Provider and infrastructure-as-code compatibility apply.Browse deployment templates
Existing resources or Terraform statePlan adoption before changing ownership or deployment workflows. Connecting an account does not automatically import every existing cloud resource.Discuss your current setup

  • A Git repository

    Connect GitHub, GitLab or Bitbucket. Run it as containers with no cluster to manage (Amazon ECS), on Kubernetes, or start from a serverless or static-site template.

    See where it can run

  • Existing Kubernetes cluster

    Connect its API endpoint and service account so Microtica can deploy applications to it. The cluster can run in your cloud or on-premise.

    See cluster requirements

  • New infrastructure

    Connect AWS, GCP, or Exoscale and choose a compatible template or infrastructure component. Provider and infrastructure-as-code compatibility apply.

    Browse deployment templates

  • Existing resources or Terraform state

    Plan adoption before changing ownership or deployment workflows. Connecting an account does not automatically import every existing cloud resource.

    Discuss your current setup

Mica in Platform

Ask about your environments. Approve what it proposes.

  • Take a repository to a live app, with one approval
  • Ship releases and promote staging to production
  • Inspect environment health, deployed versions and logs, and explain why a build or deployment failed
  • Prepare deploy, scaling and remove actions as approval cards
  • Answer in Faster mode for quick questions, or Smarter for failures and production
  • Git-push pipelines keep their own triggers. Mica does not replace them.
How approvals work

Deep investigation · Beta

Incidents beyond what you deployed here?

Mica can also investigate across your whole AWS account and clusters, whoever deployed the service. It connects read-only, finds the root cause and proposes a fix you approve. It runs in a separate app, Deep Investigation, now in beta.

Explore Deep Investigation

Try one app first.

Paste a repository and approve the plan, or bring your architecture to a demo.

Start freeBook a demo