Contact
Describe the problem. We will tell you the truth about it.
A short call is usually enough to work out whether this is a project, a small fix, or something you should not spend money on at all.
Thank you — message received.
A member of the team will reply within one business day. If it is urgent, call the number listed beside this form and say so.
Office
Phnom Penh, Cambodia
Visits by appointment. We are happy to come to you instead.
Bring these to the first call
- What the system does today, even if the answer is embarrassing
- Who is accountable if it stops working
- The compliance or audit pressure you are under, if any
- The date that is actually driving the timeline
Questions
Asked often enough to answer here.
Do you only work with large organisations?
No. A good deal of our work is for teams of five to fifty people who have outgrown passwords and shared folders but cannot justify an enterprise platform. The Root CA System and SftpS both scale down as well as up.
Can we run your products on our own infrastructure?
That is the only way we ship them. Both products are deployed inside your environment, on hardware or private cloud you control, with keys you generate. We do not hold your private keys and we do not need network access into your estate to operate them.
We already have a certificate authority. Can you just fix it?
Frequently, yes. An assessment tells you whether the existing CA can be documented, re-keyed into an HSM and brought up to policy, or whether a migration behind a new root is the cheaper path. We have no incentive to prefer one answer.
What does an engagement typically cost?
An assessment is a fixed fee and runs two to three weeks. Build work is scoped and priced before it starts, billed against milestones. Operations is a monthly retainer sized to how critical the system is. You will see numbers before you sign anything.
Do you sign NDAs?
Yes, before any technical detail is exchanged. We can work under your template or provide ours.
Which languages does your team work in?
Khmer and English for meetings and documentation. Technical deliverables are written in English by default unless you need otherwise.