Contact
Email, and no form in between. Pick the address that matches your situation — it decides who sees it first — and the notes below cover what makes a first message worth replying to properly.
Where to write
General Inquiries
Anything that does not obviously belong to one of the addresses below. If you are unsure, this is the right one — it will be passed on.
[email protected]Sales
New work, scoping, architecture questions and migrations — including anything that is not yet a project.
[email protected]Technical Support
For systems already in our care. Include the affected host or service in the subject line so it can be picked up without being read first.
[email protected]Partnerships
Referral arrangements, subcontracting, and working alongside another supplier on the same system.
[email protected]Security Reports
Vulnerabilities in this site or in a system we operate. Reaches a separate inbox rather than the support queue.
[email protected]
Business Hours
- Days
- Sunday – Thursday
- Hours
- 10:00 AM – 6:00 PM (EET)
We typically respond to emails within one business day.
What makes a first message useful
None of this is required. It is simply the difference between a reply that answers you and a reply that asks three questions back.
- The shape of what you have now — where it runs, roughly how big, and what it is built on.
- What is going wrong, or what has to be different, and what is forcing the timing.
- Which service you think this is, or that you are not sure. Being unsure is fine and common.
If something is urgent, say so in the subject line. It is the only part of a message that gets read before the message does.