EZGH Cloud is a general-purpose cloud platform. You manage it in the
console, with the ezgh CLI, or through the
API.
- Create an account: sign up, then set up your organization and first project.
- Make your first API call: create an API key and call the API with
curl.
Products
| Product | What it does |
|---|---|
| Compute | Runs virtual machine instances, with encrypted block storage volumes and snapshots, a public IPv6 /64 per network interface, public IPv4 addresses and stateful firewalls |
| Private Networks | Connects your instances over private networks: VPCs, their subnets, and network interfaces |
| Load balancers | Puts a public IPv4 address, an IPv6 address or both in front of your VPC’s instances, with TCP and TLS listeners, target groups and health checks |
| WAF | Inspects requests to a load balancer’s HTTP and HTTPS listeners with managed rule sets and rules of your own, and blocks or logs what they match |
| CDN | Serves your sites over HTTPS from locations near your visitors, with your own domains, in front of one origin |
| Kubernetes | Runs Kubernetes clusters in your VPC: EZGH runs the control plane, node groups of your instances run the pods, and Services, volumes and kubectl sign-in use EZGH load balancers, storage and IAM |
| Sandboxes | Runs isolated machines started from a container image, where you run commands and read and write files, and that suspend when idle and resume on the next call |
| Run | Serves a container image at its own HTTPS URL, starting instances as requests come and stopping them when they stop, with revisions and traffic splits |
| EZGH SSO | Gives your workforce a directory and single sign-on to your apps, over OIDC, SAML and SCIM |
| IAM | Controls who can do what in your organization: users, groups, bots, policies and API keys |
| Billing | Payment methods, credits, invoices, costs and usage for your organization |
| Trails | Records API activity in your organization, for lookup and SQL queries |
| Notifications | Emails your organization’s contacts about its resources, and keeps the notices in an inbox |
| Service quotas | Shows the limits that apply to your organization and projects |
| Secrets | Stores passwords, API keys and .env files as encrypted, versioned secrets |
| Observability | Keeps the logs, traces and metrics your services send with OpenTelemetry, and searches and queries them |
| Workflows | Runs durable workflows written as code in your own application, with steps, retries, sleeps, callbacks and schedules |
| Feature Flags | Turns features on and off in your backends and web pages, with per-environment targeting, segments and percentage rollouts, through OpenFeature |
| Container Registry | Keeps your container images on your project’s own registry host, pushed and pulled with docker or any OCI client, and pulls Docker Hub images through it |
| Git | Hosts Git repositories, cloned and pushed over HTTPS, with pull requests, branch rules, checks and Git LFS |
| Build | Runs a repository’s tasks on every push, each in its own sandbox, and skips every task whose inputs haven’t changed |
| Deploy | Describes an application in one EZGHDeploy file, and builds, plans and rolls it out on every push to an environment’s branch |
| Object Storage | Stores objects in S3-compatible buckets, used with AWS CLI, AWS SDKs, rclone and other S3 tools |
| Files | Gives the instances in a VPC shared file systems, mounted over NFS 4.1, optionally with TLS |
| Databases | Runs managed PostgreSQL, Percona Server and MariaDB databases in your VPC, with automatic failover, backups, point-in-time restore and blue/green upgrades |
| Caches | Runs managed Valkey and Memcached caches in your VPC, with TLS, users whose passwords live in Secrets, and an optional standby |
| Warehouse | Runs managed ClickHouse data warehouses in your VPC, with shards and replicas, users whose passwords live in Secrets, loading from your buckets, Kafka clusters and databases, and daily backups |
| DNS | Hosts your domains’ public DNS: zones, record sets and DNSSEC |
| Domains | Registers domain names, paid by card, with an EZGH DNS zone, nameservers and DNSSEC set up in one step |
| Fleets | Opens shells and runs commands and scripts on your Linux machines and EZGH instances, with no SSH keys, open ports or bastions |
| Queues | Keeps messages between the parts of your system in standard and FIFO queues, with long-poll receive, HTTPS push and dead-letter queues |
| Hosted Queues | Runs managed RabbitMQ and Kafka clusters in your VPC, with TLS, users whose passwords live in Secrets, and metrics in Observability |
| Private CA | Runs your own private certificate authorities and issues the certificates your services, clients and devices trust |
Accounts, organizations and projects
- Account: how you sign in. One account works for every EZGH Cloud product.
- Organization: holds your members, IAM policies, API keys, billing, Trails and projects. An account belongs to at most one organization. The account that creates an organization is its root user. See Organizations.
- Project: a container for resources inside an organization, such as secrets. An organization can have 10 projects by default. See Projects.
API paths name the organization, and the project where one applies:
/v1/organizations/{orgId}/projects/{projectId}/….
From sign-up to your first API call
- Create an account at
https://login.ezghcloud.com. - Create your organization. Setup asks for it right after sign-up.
- Create your first project. Setup asks for it next, then for billing details and a card.
- Create an API key and make your first API call.