Support
How to reach the people who run Ordo Kit, what to put in your message so we can act on it, and where the answers to the most common problems already are.
Last updated:
How to reach us #
Email support@ordokit.dev. You do not need an account to write to us.
If you are signed in, you can also use the Support form in the dashboard. It sends your message to the same mailbox, with the GitHub account you are signed in with, and we answer by email.
What to include #
- Your GitHub login: the account you sign in to Ordo Kit with.
- The project's address, for example
my-app.ordokit.dev, or your own domain if it has one. - What happened: what you did, what you expected, and what you saw instead. Copy the exact error message, and the step the progress view stopped on.
- When it happened: the date and time, with your time zone.
Never send a password, an API token (omcp_…), a private
key or a webhook secret. We do not need them to help you, and we will
never ask for them.
Common issues #
The manual's Troubleshooting section is grouped by where a run stopped, and the MCP reference has its own troubleshooting for agents and connectors. Four common ones:
The build failed
The deployment page shows our pipeline log alongside the build
output, and between them they usually name the cause. The usual
ones are COPY paths that do not match the build
context, a build that needs a secret, and running out of memory
during the build.
See Repository and build.
The certificate is “pending”
Issuance had not finished within the time the deployment waits for it. The site exists and the certificate is usually seconds away, so reload it shortly afterwards. If it never arrives on your own domain, check that the name resolves to the right host and that port 80 is reachable. See Certificates and Your own domain.
The connector will not sign in
Add https://ordokit.dev/mcp as the connector's address. Your
browser opens on our site; sign in with GitHub and approve the app
on the consent page. On the free trial you are asked to verify a
card first ($0, nothing charged). A connector that asks you to sign
in again was disconnected under Settings → Connected apps, went
60 days unused, or had its sign-in reused; connect it
again. See Connecting an
agent and MCP clients.
“Repository not found”, or no access to a repository
GitHub gives the same answer for a typo, a repository that does not exist and a private one we have not been granted. Check the owner, name and branch. For a private repository, install the Ordo Kit GitHub App on it and add the read-only deploy key the wizard shows. See Private repositories and Repository and build.
Security reports #
To report a vulnerability, email support@ordokit.dev with “Security” in the subject. Describe the issue and how to reproduce it. Please do not access, change or keep data that is not yours, and do not disrupt the service or other people's sites while you investigate.
Billing and privacy requests #
Refunds, and what cancelling or deleting your account does to billing, are covered by the Refund Policy. To see, correct or delete the data we hold about you, see the Privacy Policy. Both are handled at the same address.
Contact #
Ordo Kit (operated by IE Meshcheriakov Artem Andreevich, an individual entrepreneur)
Moldo Niyaza 2, Osh, 723510, Kyrgyzstan
Telephone: +996 755150546
Email: support@ordokit.dev