Gyro Containers concepts: environment, node, service, revision and packages
1. Concepts
| Concept | Meaning |
|---|---|
| Environment | The Gyro Containers service you order (one service = one environment). All your services, nodes, domains and registry account live inside the environment. |
| Address code | A 6-character code specific to your environment. Your service addresses look like service-name-code.gyroapp.net. |
| Node plan / node pool | Virtual servers dedicated to you. The nodes in your package run only your services. Your capacity is the sum of your nodes. |
| Service | An application you run: a Docker image + port + size + variables. An environment can hold several services; they talk to each other over an internal address. |
| Replica (instance) | The number of running copies of a service. Raising the replica count (scaling) raises capacity and resilience. |
| Revision | Every release (a change to the image, size, command or variables) is a new revision. The last 15 revisions are kept and you can roll back to any of them. |
| Environment variable / secret | Settings you give the application. Secrets are stored encrypted and never shown again. |
| Image registry | A private registry owned by Gyro where you can push your images (optional). Pulling from Docker Hub and GitHub is also free. |
Addresses: Every public service gets https://service-name-code.gyroapp.net. Services in the same environment reach each other at the internal address http://service-name; an internal address does not need to be public.
2. Packages
Price = environment fee 4.99 €/month + the monthly price of each node. Node prices equal Gyro Cloud Istanbul / Turkey VDS plans. Prices exclude VAT, are based on euros and fixed; TRY is calculated at the current rate. Hourly price = monthly price ÷ 672 (price calculation).
| Package | Nodes | Monthly cap | Max services | Max replicas per service | Max domains per service |
|---|---|---|---|---|---|
| Starter | 1 × (2 vCPU / 4 GB) | 10.98 € | 10 | 5 | 5 |
| Standard | 2 × (2 vCPU / 4 GB) | 16.97 € | 20 | 10 | 10 |
| Pro | 3 × (4 vCPU / 8 GB) | 36.46 € | 40 | 20 | 20 |
Capacity you can use: a system share of 0.25 vCPU and 768 MB is taken from each node. For example on Starter, 1 node × (2 − 0.25) = 1.75 vCPU and about 3.3 GB of memory remain for your services. One replica of a service cannot be bigger than one node's capacity.
In addition to the environment fee, 2 GB of the image registry is free; above that it is 0.05 €/GB per month (Gyro image registry).
3. How to choose a service size
For each service you choose CPU and memory per replica (default 0.25 vCPU and 256 MB). The panel has CPU / replica and Memory / replica fields; on the command line it is in thousandths (--cpu-m 250 = 0.25 vCPU, --memory-mi 256).
- CPU and memory are reserved (guaranteed). Memory use above the reservation makes the container stop (OOMKilled); CPU above it slows the container down.
- Total = replicas × replica size; it cannot exceed your pool capacity. If it does the panel says "Not enough capacity in your node pool".
- Start small (0.25 vCPU / 256-512 MB), watch the logs and graphs and increase if needed.
4. Growing your plan
For more capacity you can move to a higher package; extra nodes are opened and capacity grows. The plan options appear on the order screen. If the service has no plan-upgrade option, open a support ticket. A downgrade that would fall below the capacity used by running services is rejected; reduce the replica count or size first.
5. Frequently asked questions
Are my nodes shared with other customers?
No. Nodes are dedicated to your environment; network traffic between environments is isolated as well.
How are the service name and address formed?
The service name uses lowercase letters, digits and - (up to 40 characters, starting with a letter). The address: name-code.gyroapp.net.
Can I run several services in one environment?
Yes, up to the number of services allowed in the package (10/20/40).
Which package should I choose?
Starter is enough for one small web service. For resilience, at least two replicas and two nodes (Standard) are recommended: if one node goes into maintenance, the service keeps running.
Next step
Thanks for your feedback!