The Ecocloud platform
Build your application environment.
Choose a compute runtime, connect your services and manage them from one console.
Choose your starting point
The right runtime starts
with your application.
Keep the operating system close, bring a packaged service or give one HTTP task its own deployment. Choose around the work you need to do.
| Your decision | Virtual machines | Containers | Functions |
|---|---|---|---|
| Start with | A Linux operating system | A compatible OCI image | A request-driven task |
| Deployable artifact | Guest image with optional cloud-init | Versioned application image | Function source and configuration |
| Access model | Guest SSH and browser console | Configured service ports and log views | Configured HTTP invocation endpoint |
| Useful for | Custom stacks and self-managed databases | Web services, APIs and workers | Webhooks and focused HTTP logic |
| You maintain | Guest OS, packages, application and data | Image, dependencies, configuration and data | Handler, dependencies and invocation access |
| Review before choosing | Image, resources, storage and access | Image compatibility, ports and persistence | Execution limits, endpoint and billing unit |
A workload can use more than one runtime. Connect services around their responsibilities and data needs.
Explore application patterns ↗One platform
Understand how the pieces connect.
Run the application in the environment it needs, connect its dependencies and give the endpoint a domain name. Use the console to follow service operations and Cloud Shell for supported CLI tasks. Each product has a distinct role in the same application.
Logical relationships between platform components. Available features depend on the selected service and environment.
Your next step
Your next application starts here.
Explore the available configurations and choose the right foundation for your project.
Create account