Mapt is a swiss army knife for provisioning environments, the project is focused on cover 3 main purposes:
- Offer a set of target environments / services with different topologies across multiple cloud providers.
- Implement best practices leading to increase cost savings, speed up times and security concerns.
- Easily integrate targets with different CI/CD systems or with local envs to facilitate developers testing experience.
Mapt offers a set of instances categorize by the OS, instances can benefit from spot module which will allocate the machine on a region with a good relationship beetween cost / availability. Also and depending on the type of instances it will use specific best practices to boost the provisioning time (i.e Fast Launch, Root Volume Replacement, ...).
Instances can be wrapped on specific topologies like airgap, in this case mapt will set the target isolated and will create a bastion to allow access to it.
Instances can also define a timeout to avoid leftovers in case destoy operation is missing. Using this approach mapt will be execute as an unateneded execution using servless technologies.
MacOS-Windows Server-Windows Desktop-RHEL-Fedora-Ubuntu
Mapt offers some managed services boosted with some of the features from the instances offerings (i.e spot) and also create some ad hoc services on top the instances offerings to improve reutilization of instances when there is no easy way to do it (i.e. Mac-Pool).
AKS-Mac-Pool - OpenShift-SNC - Kind
Currently each target offered by Mapt can be added as:
And Tekton taks are offered to dynamically provision the remote target to use within tekton pipelines