DevOps and cloud infrastructure — find a DevOps engineer
You need a DevOps engineer when every release is still deployed by hand, the cloud bill grows for no clear reason, or your app has to move to AWS, GCP or Azure. Describe your stack and task, and engineers will send you responses. Or pick one yourself — by services, portfolio and client reviews.
DevOps engineers
How much DevOps services cost
What affects the price
The state of the project
Setting up a pipeline for one service with tests is simpler than untangling an undocumented project that is still uploaded to the server by hand.
Environments and services
Separate dev, staging and production, several microservices, queues and databases multiply the configuration and testing.
Migration with or without downtime
A move that takes the app offline for a night is simpler than a zero-downtime migration with data sync and gradual traffic switching.
Cloud resources are separate
Servers, databases and traffic in the AWS, GCP or Azure cloud are paid at the provider's rates, separately from the engineer's work.
One-off setup or ongoing support
A turnkey setup and monthly support with incident response at night and on weekends are priced differently.
Prices come from specialists' profiles on Nexperity and update automatically. You agree the final price with the specialist directly.
How to find a DevOps engineer
Two ways — pick the one that suits you
Pick a specialist yourself
- 1Open specialists' profiles and their work
- 2Send a request that describes the task
- 3Once accepted — contact the specialist directly
Post an order
- 1Describe the task, payment and the timing you want
- 2Receive responses from specialists
- 3Pick the best specialist and agree directly
- Free for clients
- Orders can be posted anonymously
- Your contacts open only after acceptance
- No commission on the deal
How to choose a DevOps engineer
- 1
Experience with your stack
AWS, GCP and Azure have different services, and Kubernetes or Terraform are separate skills. Look for an engineer whose services and portfolio include exactly your stack.
- 2
Access with minimal permissions
Create a separate account for the engineer with only the permissions needed instead of root access or a shared password, and close it once the work is done.
- 3
The infrastructure belongs to you
The cloud account, the repository, and the Terraform and pipeline configurations should belong to you, not to the engineer.
- 4
Backup and rollback plan
Before a migration, ask how the engineer will back up the database, test the restore and what they will do if something breaks after the switch.
- 5
Documentation after the work
Agree that you will get a description of the infrastructure and deploy and rollback instructions, and that passwords and keys will not be kept in the code.
What to put in the order
What you need: CI/CD, migration, Kubernetes, monitoring or an audit
The stack: language, framework, databases and queues
Where the app runs now and where it is moving: AWS, GCP, Azure or a VPS
Where the code is kept: GitHub, GitLab or Bitbucket
The load on the app, and whether it can be stopped during the work
Payment, timeline and whether you need support after launch
Questions about Nexperity
How Nexperity works — separately for clients and for specialists
For clients
Nothing. Searching for specialists, sending requests, posting orders and receiving responses are free.
No. You agree the price and the payment method with the specialist and pay them directly. Nexperity does not take payments and is not a party to your deal.
A request goes to one specialist — from their profile. An order is posted for everyone: specialists send you responses, and you choose which one to accept.
How the specialist will do the task, a price — fixed, a range, hourly or “on request” — and, optionally, an estimated timeline.
30 days from publication: all that time it is visible in the feed and specialists can send responses. The exact end date and time are shown on the order in your account. From that moment the order is closed and a response can no longer be accepted. You can cancel it earlier, and if no specialist turned up, post a new one.
Yes: you can hide your name and photo in an order. The anonymity lasts until acceptance — the specialist whose response you accept sees your name and photo. The task description is public: anyone visiting the site can read it.
Only after acceptance — when you accept their response or they accept your request. And only the contacts you chose to show.
After acceptance you see the contacts the specialist chose to show, and they see the ones you chose. You can also message on Nexperity when the chat is on: on an order you decide that, on a direct request the specialist does.
Once the work is done, mark the order or the collaboration completed in your account — then you can say whether you recommend the specialist. A review can only be left for a collaboration that happened through Nexperity: one per specialist, which you can change or delete at any time.
For specialists
Nothing for now: this is the free period, and no subscription is needed yet. Nexperity takes no commission on deals — you settle with the client directly.
Sign up, fill in your specialist profile and add your services — each with a category, a description and a price. Once the profile is complete, it appears in search and on the category pages.
Two ways: clients send you requests from your profile, which you can accept or decline; and you see public orders in your categories in your account and can respond to them.
You describe how you will do the task and give a price and, optionally, a timeline. The client compares responses and accepts one.
Contacts set to “Public” are visible to everyone on your profile. A client sees contacts set to “After connection” once you accept their request or they accept your response. “Hidden” ones are not revealed in new connections: a contact already revealed to a client stays visible to them.
Each service has a fixed price, a range, an hourly rate or “on request”. Prices show on your profile and in search results, and you agree the final price with the client.
Through search and the category pages of your services. The order depends on your clients' reviews — how many of them recommend you — and in search also on how well your services match the query.
A photo, a description, your region and way of working — online or in person — your contacts and a portfolio: photos of your work, each with a short caption if you like.
A client leaves a review after completed work, and only for a collaboration through Nexperity: they say whether they recommend you and may add a few words. Each client counts once, however many times you work together.
Related categories
Are you a DevOps engineer?
Get orders from your category and respond to them — with no commission on deals.