- Development
- Deployment
- Diagnosis
Objective
The goal of this section is to describe the processes, internal and external that companies have requested in from our years of experience in veriety of industries with complex applications and infrastructer. We aim to help you build confidence to determine if Ardor is a good fit for your company. Ardor maintains a policy to be forthcoming and frank at all times. We would rather have a developer make the correct choice for their company than to adopt Ardor and then come to regret that decision. If you have any additional questions or if you require any additional disclosure you can contact us to set up a call at info@ardor.cloud.Product Philosophy
Ardor is focused on building an amazing developer experience. Our goal is to enable developers to deploy their solutions and see their work in action, without thinking about platform research, CI/CD, deployments, networking, and so forth, until they need to.Take What You Need
To achieve our goal, we’ve designed Ardor to “just work”, with all the necessary magic built in to achieve that. Ardor at a high level is a cloud that build, deploy and operate your solutions. Or read your code repo, makes a best guess effort to build it into an OCI(Open Container Initiative) compliant image, and runs the image in cloud in severless manner.- Have idea of a agentic application but not sure how to build it? Cerebrum will help you. Just explain your needs and idea and let Cerebrum create a PRD, build your solution, and deploy it to the cloud.
- Have a code repository but have yet to think about deployment? We got you. Connect your code repository and let Ardor take care of the rest.
- Already built the perfect Dockerfile? Bring it. If you have a Dockerfile in your repo, we’ll find it and use that to build your image.
- If you’ve outgrown the “magic” built into deployment platforms, or are suspicious of things that are just too magical, we are happy to provide a high level overview of our architecture.
Leave What You Don’t
Streamlined deployment workflows and sane defaults are inherited by every project in Ardor out of the box; but as a team of engineers, we at Ardor are very aware that what works for one project does not always work for another. Or sometimes, you just need to be in control - maybe you already have a workflow you like, or maybe you need to layer Ardor into existing infrastructure, and abstractions only get in your way. That’s why we’ve designed the platform for flexibility, wherever you need it. On Ardor, you can use the default pattern for deployment or opt to use vendor. In fact, we will even support you in your effort to integrate Ardor in a unique way. Here are a couple of use cases we’ve helped customers take advantage of:- Deploying to Ardor from Gitlab CI/CD
- Supporting the development of a Terraform provider
- Region based routing to workloads via Cloudflare