Provision and maintain
Create resources and use the lifecycle actions available for the selected service.
Platform architecture
Know what runs your application.
QEMU/KVM virtual machines, Podman workloads and PowerDNS naming services. Configure resources, connect services and inspect their state from one console.
Architecture
One console. Distinct building blocks.
Choose the runtime for each part of your application. The control plane coordinates resource operations; your software runs in the VM, container or function you configure.
- Compute
- Virtual machines, containers and HTTP functions
- Connectivity
- Networks, subnets, routing and firewall rules
- Naming
- DNS records and supported certificate workflows
- Operations
- Service views, console access and Cloud Shell
ConsoleCloud ShellSupported API reads
Ecocloud control planeConfigure · inspect · operate
Virtual machinesQEMU / KVM
ContainersOCI / Podman
FunctionsHTTP workloads
Networks & firewall rulesDNS & certificates
Logical relationships between platform components. Available features depend on the selected service and environment.
Technology
Familiar tools at each layer.
Keep your Linux packages, OCI images and DNS records. Each technology has a specific role in the platform.
- QEMU / KVM
- Virtualization for the guest operating system you administer.
- Podman / OCI
- Container runtimes for packaged application services.
- PowerDNS
- Authoritative DNS zone and record management.
Operate the environment
Configure. Inspect. Verify.
Track the platform operation, then check the application. A completed resource change is only one part of a successful release.
- 01Submit the configuration
Review the selected resource and submit the change from the console.
- 02Follow the operation
Inspect its resulting state and available logs.
- 03Test the application
Verify access, dependency connections and an actual application request.
Connect and name
Configure intended network paths, DNS records and supported certificate bindings.
Inspect and troubleshoot
Use service state, log views and Cloud Shell. Public status provides a separate view of monitored platform services.
Before deployment
Define what your team will operate.
Match the selected offer to your resource, connectivity and maintenance requirements.
- Platform
- Resource provisioning, configuration workflows and supported operating tools.
- Your team
- Application software, credentials, data backups and recovery testing.
- Selected offer
- Resources, location, connectivity and contractual service commitments.
Your next step
Start with the workload. Build a clear plan.
Tell us what you run, how it connects and what your team needs to operate it.
Discuss your requirements