Start with a diagnosis
Contact runs through one channel: email to contact@ruocent.com. There is no web form. Target regions, current URL, content type, and the sharpest problem — these are enough to start; a full specification is not needed. We then check scope and reply with next steps. Passwords, private keys, identity documents, and full customer datasets must not be sent by email.
- Target access regions
- Current website or server URL
- Expected content type and traffic
- Whether domain, certificate, and storage already exist
- Budget range and preferred start time
| Stage | What Ruocent does | What we may need from you |
|---|---|---|
| Initial review | Check completeness and public access state | Primary URL, regions, most urgent problem |
| Scope | Separate delivery, resource cost, ongoing ownership | Current architecture, volume, internal owner |
| Route & quote | State approach, deliverables, boundaries, timing, price | Confirm priorities, budget, authority |
| Implementation | Establish change, acceptance, handover records | Provide staged material, approve key decisions |
How quickly will an email receive a reply?
Complete and specific requests are reviewed first. Complex migration cannot be quoted reliably from one email — the first reply may list the material and inspection needed.
Can we contact you without a final budget?
Yes. Business stage and a realistic investment range determine whether to validate, diagnose, or defer. An exploratory email is not a project commitment.
Will our project be published as a case study?
Not without explicit authorization. Silence is not consent. Customer names, marks, system details, and identifying results remain private.
What should never be in an email?
Passwords, private keys, payment card numbers, identity documents, and large personal datasets. For these we arrange a separate transfer method first.