Cloud server
Cloud ServerVirtual servers you create in the panel and pay for hourly
GitOps takes your code from a Git repository and deploys it to Kubernetes. You always know which version is running.
The selected Artifact is deployed, and you track its synchronization status in the panel.
Version 1.4.0 is now running. Versions and commit IDs are examples only.
Every step from image to running application is recorded in the panel. Images are built in your CI system; Dorsa Cloud provides the Repository, security scanning and deployment.
Create an Application for each software project. Each Application has a dedicated Repository for images.
Your CI system pushes the image to the Repository using that Application's credentials.
Pushed images are registered as Artifacts in the panel. Run a security scan for each version and review its report.
Deploy the selected version or promote it to the next environment, and track synchronization status.
Each Artifact is a deployable version. Run a security scan and review its report before deployment.
Every change to deployed software creates a history entry with a version number, change type, status and commit ID.
Review synchronization status, history and resources created in Kubernetes from the panel.
With every version recorded, returning to a healthy release is a simple panel action rather than manual server work.
Select an applied or superseded version to deploy it again. The rollback creates a new history version; nothing is deleted.
Move a version from one environment to the next, such as test to production. History records this change as a promotion.
If the running state differs from the recorded state, run synchronization again from the panel.
Keep building images where you do now; only the image destination and deployment workflow change.
Each Application has separate history, showing which version runs where.
Require the responsible person's approval for sensitive deployments.
The main capabilities of GitOps delivery at a glance.
Configure the code repository, artifact storage and deployment settings in one place.
View built versions, run a security scan for each version and review reports in the panel.
Update, roll back, promote to the next environment or cancel from the panel.
Require the responsible person's approval for sensitive deployments.
Services commonly used alongside GitOps delivery.
Virtual servers you create in the panel and pay for hourly
Cloud storage for files, photos and large datasets
When code, built versions and servers are managed separately, it becomes unclear which version runs where and releases become risky.
GitOps delivery supports use cases such as Kubernetes deployment, Version management, Promote from test to production. The right choice depends on your project's technical and operational requirements.
Read the product guide and estimate costs in the calculator, then create the service in your chosen project in the client panel.
Register, estimate costs before provisioning and pay hourly for the time you use the service.