Pricing
Working out the problem and estimating it costs nothing. Paid steps start at 3 000 ₽: four directions below, each with packages of a fixed scope. The exact figure follows the brief and the solution outline.
Where it starts
The audit comes off the project price if the work continues.
Cloud infrastructure end to end
For a single service, an MVP, an internal tool. One server, no Kubernetes.
- Docker Compose instead of an orchestrator
- Deploys from Git on push
- Monitoring with alerts to Telegram
- Backups
- VPN for server access
- Domain and automatic certificates
The service stops living on a developer’s laptop, a deploy takes a minute, and you hear about an outage at once.
Moving up to “Start” later comes with credit for what is already done.
For a startup or a team that needs real Kubernetes from day one. One environment.
- Kubernetes
- Docker image registry
- S3 object storage
- Database
- GitLab CI or GitHub Actions with deploys
- Monitoring, logs and alerts
- VPN for the team
- Domain and automatic certificates
Deploy by button instead of ssh by hand, you can see what the service is doing, certificates never lapse.
For a product with several services and a real production. Everything from “Start”, plus:
- Three environments: dev, stage, prod
- Load balancing and autoscaling
- Backups with restore testing
- Secret storage instead of passwords in code
- Single sign-on across services
- GitOps deploys
- Dashboards for your own metrics
A release does not take production down, capacity follows the load, and the backup is tested rather than merely configured.
For a closed network and real resilience requirements. Everything from “Team”, plus:
- Highly available cluster
- Database replication
- Closed network reachable only over VPN
- Access control over company assets
- Load testing before launch
- Documentation and handover
Losing a node does not take the service down, data survives losing a server, and the load ceiling is known in advance.
Cloud bills, licences and domains are paid by you directly — they are not part of the quote.
Support
The minimum that makes sure you hear about a problem before your users do.
- Monitoring and alerts
- Response during working hours
- A monthly report
The service is watched, at the price of an occasional sysadmin.
Everything from “Watch”, plus regular work:
- Updates and backups
- Releases
- Response under an 8/5 SLA
- 10 hours of work a month
The system needs no remembering: updates, releases and backups happen on their own.
Everything from “Support”, plus moving the system forward:
- On-call
- Changes and new features
- Cloud cost optimisation
- 30 hours of work a month
The system keeps developing, and the cloud bill does not grow by itself.
Work beyond the package is billed hourly at a reduced rate. No lock-in: you can stop any month.
AI at work
Keeping AI running costs 30–40% of the build price a year: models change, prompts and the knowledge base need work. That is the market norm, not a markup.
Development
How the quote is worked out
- Brief. What you need, what the constraints are, what the budget is. Free, 40 minutes.
- Range. A from–to figure and the scope of work by email within 1–2 days. No strings attached.
- Solution outline. For larger work — an audit or design phase, credited against the project price.
- Quote. The base package plus add-ons and multipliers. Fixed before the work starts.
- Payment. 30% to start, 40% midway, 30% on acceptance. Support is billed monthly. Three months of warranty.
What is never in the quote
Cloud bills, licences, domains and paid APIs. You pay for those directly from your own account: the true cost of ownership stays visible, and you pay no markup.
Tell me about the problem and I will come back with a range and a scope.