What you can use this page for
This site is a reference, not a service. You can use the contact route, once it is open, to report an error in an article, to suggest a topic the reference should cover, or to ask a general question about a hosting architecture or a migration approach. A reply is not promised, and nothing sent here creates a commercial relationship.
What this site cannot help with
- Choosing or recommending a supplier. The site names none and ranks none.
- Quotations, pricing or availability. It sells and brokers nothing.
- Operating, monitoring or repairing your systems. It has no access to any environment and does not offer an operational service.
- Auditing, scanning or certifying your infrastructure. The planner works only from answers you type in.
What to include
A useful message says in general terms what you are trying to decide or move: the kind of workloads, the rough scale, and the constraint that worries you most. If you are reporting an error, give the article, the passage and what you believe is correct.
What never to send
Do not send passwords, access tokens, API keys, private keys, multi-factor codes or recovery codes. Do not send configuration files or logs that contain them. Do not send personal data about your customers or staff, internal network diagrams that identify exposed systems, or anything covered by a confidentiality obligation. Describe your situation in general terms instead. Nothing you need to ask depends on those details.
How to get in touch
The direct contact channel is shown below this text. Until a contact address has been published, there is no way to send a message from this page, and no form appears, because a form with nothing behind it would only look as though it worked.
The direct contact channel is not open yet. There is no form on this page because nothing is connected to receive one, and a form that appeared to work would be misleading. When a contact address is published it will appear here.