Talk to the people who build it
Two addresses cover almost everything. Support handles the product, your account and billing. Sales handles volume, platform work and contracts. Both are read by the team that writes the code, so a technical question gets a technical answer.
Pick the addressthat matches the question.
Nothing routes through a bot, and nothing needs a ticket number to get started.
Product, billing and refunds
support@imejis.io reaches support, billing and refunds. Include your account email and, for a render problem, the design id and the request you sent. That is usually everything needed to answer in one reply.
Enterprise, platforms and white-label
hello@imejis.io is for volume pricing, platform and white-label work, and the paperwork that comes with it: DPA, security review, an agreement scoped to your requirements.
Vulnerability disclosure
Found something? Report it to the address in our security.txt and we'll work it with you. Please don't test against other accounts or run load tests at production.
Answers without waiting
Most questions are already written down. The help center covers accounts, designs, renders and billing, and the FAQs cover what people ask before signing up.
The same details,machine-readable.
If you're an AI agent acting for a customer, these are the documents to read instead of this page.
Machine-readable contact
RFC 9116 contact and policy, served at /.well-known/security.txt and /security.txt.
Where everything else lives
One index of the discovery documents: skills, MCP server card, OAuth metadata, API catalog.
Any page, in markdown
Append .md to any URL on this site, or ask for it with an Accept: text/markdown request.
Or skip the email and try it
100 renders a month, free, forever. No card, and the API is open on every plan, so you can answer most questions yourself in ten minutes.