Contact us

Pricing

Pricing policy

When you have the turnkey service, the most important advantage is a guarantee that everything will be done at any time to ensure your infrastructure operability despite the circumstances and formal limits.

That is why at the core of our pricing policy is a monthly fee with a focus on long-term business relations. This grants you:

  • the confidence that we will always support you in any critical situations;
  • the predictable budget planning regarding our services.

As for us, it is:

  • a strong motivation to offer better services, thus you will be interested in our long-lasting cooperation;
  • the way to capitalize the projects we maintain despite the periods of intensive work (e.g. building/transforming the infrastructure at the early stages) when we spend far more resources than regular subscription fees.

Math behind

We do not directly use the staff time for billing purposes since we know that the performance of every employee is always subjective.

Thanks to the large number of projects we have gathered detailed stats that allow us to estimate costs per project. It is a function of several factors, such as:

  • the complexity of the application architecture;
  • location, size, and complexity of the infrastructure;
  • number of used technological components;
  • number of developers and their skills;
  • the difficulty of adapting the project to our existing DevOps processes;
  • the factual loads (requests per second) and data volumes.

Auditing a new project, we use our accumulated experience to estimate the expected labor input and maintenance costs.

Service cost examples

In order to get a sense of our pricing policy, please refer to the following examples that illustrate possible prices for a few abstract projects of different sizes. Please keep in mind that these are not our rates but just examples.

  • Example A (size XS)
    €3,500.00 per month
    Total production workload (in K8s)
    Low. CPU: 4 cores; RPS: 100; traffic: 25 Мbps
    Number and diversity of configurations
    One-component application. Usually, it is a single backend or backend + frontend. Cron jobs are possible.
    Number and technical complexity of infrastructure components
    2-3 runtime dependencies (standalone, replication)
    Infrastructure components' workload and size
    A small volume of data; low load. Data: 10 GB, RAM: 12 GB, CPU: 4 cores, QPS: 50
    Complexity of CI/CD processes
    Low (production plus 1-2 testing environments)
    Infrastructure size
    3-5 nodes
    Number of contact persons, developers
    Usually, several developers and one contact person
  • Example B (size M)
    €7,500.00 per month
    Total production workload (in K8s)
    Low or medium. CPU: 20 cores; RPS: 1000; traffic: 120 Мbps
    Number and diversity of configurations
    Application comprising up to 10 components (including small microservices) or medium-sized monolithic system
    Number and technical complexity of infrastructure components
    5-7 runtime dependencies (standalone, replication) including up to 3 high-availability clusters (HA failover, HA cluster, etc)
    Infrastructure components' workload and size
    Small or medium volume of data; low or medium load. Data: 150 GB, RAM: 80 GB, CPU: 16 cores, QPS: 300
    Complexity of CI/CD processes
    Average (production, several test environments, review environments)
    Infrastructure size
    1-2 clusters, 5-10 nodes
    Number of contact persons, developers
    Usually, a single team of 3-7 developers, several contact persons
  • Example C (size XL)
    €19,000.00 per month
    Total production workload (in K8s)
    Medium or high. CPU: 150 cores; RPS: 50000; traffic: 4 Gbps
    Number and diversity of configurations
    Large microservice architecture (20 to 50 services) or large monolithic system
    Number and technical complexity of infrastructure components
    10-15 runtime dependencies (standalone, replication) including up to 10 high-availability clusters (HA failover, HA cluster, etc)
    Infrastructure components' workload and size
    A medium or large volume of data, medium or high load. Data: 5 TB, RAM: 512 GB, CPU: 150 cores, QPS: 5000
    Complexity of CI/CD processes
    High (production, many additional test environments, review environments, high-level tests)
    Infrastructure size
    2-3 clusters, 20-50 nodes
    Number of contact persons, developers
    Usually, 20-30 developers and 6-10 contact persons