Comment on page
OpsCanvas is tackling the complexity of DevOps by providing tools to make it easy for software teams to focus on their primary goals, and putting IaC development under the hood.
Deploying software to the cloud is difficult. A lot of effort has been made to give operators the tools required to provision infrastructure and launch applications to the cloud in a secure, reliable, and repeatable manner. It's become table stakes in the industry.
The technology advancements that enable this type of automation are awesome. However, they come with a significant draw-back that is particularly difficult for smaller teams to overcome - namely the need to know an entire separate stack (OpenTofu/Terraform, Kubernetes, Helm, CDK, etc...) that is orthogonal to the business problem the team is trying to solve.
OpsCanvas is a platform that allows software teams to deploy software based on a logical application architecture diagram, an artifact all teams should have. In OpsCanvas a diagram consists of 3 things:
- 1.Private services - these are the services created by your team, packaged as docker containers, and stored in a private container registry.
- 2.Managed services - these are metered services from your cloud provider, they can be anything from a managed database to a natural language processing AI.
The diagram is a directed graph of nodes that represent how these services interact when running. Specifically, the direction of the connections is from the private services you've created to the other services included on the diagram.
The basic steps for deploying software using OpsCanvas:
- 1.Create a new diagram
- 2.Add managed services to it, such as AWS-managed databases
- 3.Add your services (upload container images to OpsCanvas)
- 4.Connect services on the diagram
- 5.Configure connections properties on your private services
- 6.Configure deployment options
After you create an application diagram, OpsCanvas automatically generates and manages the IaC needed to deploy and update environments. It then sets up a GitOps-style workflow to deploy your app.
- The underlying configuration code that the platform generates is based on best practices and is battle-tested.
- It’s easy to deploy the same application into multiple environments (i.e. dev, test, stage, prod), clone existing environments, or change an application’s topology and deploy that version.
- Our automation provides guardrails that prevent configuration mistakes that are all too common.
- Increased deployment velocity
- Reduced lead time
- Lower change failure rate
- Increased visibility into your cloud assets
- Role-based access control
- User audit history