Faq

What is Microtica?

Microtica is a tool that automates cloud infrastructure and application delivery. Microtica covers both CI and CD with native Kubernetes integration and AWS CloudFormation.

How is Microtica different from tools like Jenkins, CircleCI and GitLab CI?
The biggest difference between Microtica and these tools is that Microtica is more focused on abstracting complex cloud and Kubernetes integrations supported natively in the platform and in the same time providing all core features for optimal CI and CD. The other tools usually require the use of other provisioning tools and you need to write most of the scripts to make pipelines work. Microtica provides cloud infrastructure setup and application lifecycle. Having them both you can deliver your ideas in the cloud with just one tool.
How is Microtica different from Terraform and AWS CloudFormation?

Terraform and CloudFormation are tools for defining and provisioning infrastructure in the cloud in a declarative way (IaC). Microtica uses IaC engines under the hood to enable structured and reproducible cloud infrastructure provisioning.

On top of it, Microtica provides the whole lifecycle management (build/test/deploy) automation and easier distribution of infrastructure pieces. This means that you don’t have to worry about integration with these tools and all the pain points that come along.

Do I have an option to opt-out and continue to use Microtica provisioned infrastructure and applications?

Microtica provisions infrastructure using IaC (CloudFormation) on your designated AWS account. So, if you decide to opt-out from Microtica, the whole infrastructure will still stay and continue to operate on your own cloud account.

Do I need an AWS account?

Yes. All cloud resources and applications that you deploy are provisioned on your own AWS account.

Does Microtica work with other cloud providers?

Currently Microtica has native support for AWS. Support for other cloud providers is on our roadmap.

Where do you store data?

We provision cloud resources for you in your AWS account. For example, if we provision a database for you, that database is on your AWS account, so you have the ultimate access control of it. In addition, all data that is marked as sensitive is stored on your own AWS account.

Do you store my source code in Microtica?

No. We store the source code in your designated cloud account.

To enable high availability and stability, we only keep the operational files (validation schema and pipeline definition) privately in our cloud account. The best way is to exclude any private or sensitive data from those files.

How does Microtica pricing model work?

We bill Microtica per project. One project is enough to handle the entire infrastructure and applications for small, medium, and even large projects. In one project, you can have multiple environments, Kubernetes clusters, and an infinite number of teammates.

Microtica also provides a freemium plan which is suitable for individual developers and smaller projects.

Each project has its own billing lifecycle.

Where are my pipelines executed?

Microtica Pipeline can have one or more pipeline steps. To enable high availability and stability, the workflow orchestrator for those steps runs on our cloud, while steps where the actual build, test, package or any other custom instructions run on your cloud account.

Does Microtica support declarative pipelines?

Yes. We use microtica.yaml from your source code as the only source of truth for the pipeline definition.

Can Microtica trigger automatic build/deployment on each commit?

Yes. There is a possibility to opt-in for automatic builds and deployments. You can also define a trigger based on branch filter.

Where are my Docker artifacts being stored?

Currently, Docker artifacts are stored on your own AWS ECR. Support for other Docker repositories is on our roadmap.

Can Microtica set up complete Kubernetes infrastructure on my AWS account?

Yes. Microtica provides a set of free-to-use components for Kubernetes. You just need to configure them to meet your needs for scaling and availability and initiate deployment. No need for any additional coding.

Can I manage my Kubernetes applications directly from Microtica portal?

Yes. Microtica provides integrated Kubernetes Dashboard from where you can deploy and monitor your applications.

Can I execute my custom Kubernetes spec?

Yes. Even though we provide default Kubernetes spec for your applications, you can provision your applications with a custom setup if you need that. Simply add the kube.config file in your source code in root dir and Microtica will take care of executing your spec.

Can I deploy on my existing Kubernetes cluster in AWS?

Yes. You just connect your existing cluster by providing an access URL and a secret token.

Do you support deployment to Kubernetes clusters on Azure, GCP etc.?

Yes. You can connect your existing cluster on Azure, GCP or on-premise.

One thing to note is that since we currently store Docker artifacts on ECR and it does not support cross-cloud access, you will need to define other source for Docker images in Kubernetes spec.

Is there an easy way to replicate my whole infrastructure setup?

Yes. Microtica provides an environment replication feature that enables one-click replication of existing cloud infrastructure. This is usually very useful for temporary environments (e.g. performance testing).

Can I start provisioning complete cloud infrastructure without having to code anything?

Yes. Microtica provides a set of ready-to-use infrastructure components that you can just pick up and use. No need for additional coding.

Can I receive notifications on 3rd party communication tools?

Yes. Microtica supports integration with Slack. You can also receive notifications in the app directly.