Available for new work

Let's build something solid.

Tell us what you're building. We'll reply with questions, not a sales pitch — then a plan you can hold us to. Remote worldwide, start immediate.

Taking a small number of new engagements. We reply within one business day, usually sooner.

How every project starts

Design doc first — Architecture, scope and trade-offs written down and approved by you before any code is written.
Milestone-based — Work is split into clear milestones. If the first milestone isn’t what we agreed, you don’t pay for it.
No lock-in — ever — Everything is code in your repositories, documented, with runbooks. It runs without us; that’s the point.

What happens when you hit send

The form posts to our own gateway at api.deplyra.com. There is no third-party form service in the path; we removed the one we used to rely on because it exposed the destination address in the page source and kept no delivery log we could query.
Your enquiry is recorded on our side before anything is sent, so “did it arrive?” has an answer we can actually check.
It is then emailed to [email protected], a monitored mailbox, with reply-to set to your address. When we answer, you get a normal email you can just reply to.
What you type is used to reply to you, and for nothing else. There is no newsletter, no marketing list, and nothing is shared or sold. The details are in the privacy policy.
If the form fails, or you prefer email, write to help@deplyra.com directly. Same mailbox, same people, same reply.

What makes a first message useful

The stack, roughly: which cloud, whether Kubernetes is involved, what CI you run. One sentence is plenty.
The pain in your own words: a scary deploy, a bill that grew, an outage nobody could explain. We would rather hear the symptom than a diagnosis.
Any deadline that is real. It changes what we propose first.
What you should expect back: questions first, then a short written plan with a fixed quote. Never a canned pitch, and no obligation either way.