Something broken, or something to plan?
Open a ticket and it goes to an engineer who can read the codebase — not a first-line queue. Email and portal tickets land in the same place.
Submit and track tickets, see replies, and keep the whole thread in one place.
Open a ticket →Email lands in the same queue as portal tickets and threads onto the same conversation.
Send an email →For urgent production incidents on stores we already operate.
Call the team →What happens after you hit send
Retainer clients have a named engineer and an agreed window. Everyone else gets a triaged reply — with an honest answer if it is not something we should take.
Answers to what we get asked most
How do engagements usually start?
With an audit. We read the store, the code, and the data, then send written findings and a scoped plan. You keep the findings whether or not we go ahead.
What is the smallest project you take?
Fixed-scope projects generally start around two weeks of engineering. Below that, a retainer is usually a better fit than a project.
Which time zones do you cover?
The team is based in India and delivers across India, Singapore, the US, and Canada. Overlap hours are agreed at the start of the engagement.
How do I raise an urgent production issue?
Open a ticket from the Help Centre and mark it urgent, or email support directly. Retainer clients have a named engineer and an agreed response window.
Do you support stores you did not build?
Yes, after an audit. We need to understand the codebase before taking responsibility for its uptime.
What happens to my tickets if I email instead?
Email into support lands in the same queue as portal tickets and threads onto the same conversation, so nothing is tracked in two places.
Will an AI agent be able to change my store on its own?
Only within the tool scope you approve, and anything customer-facing waits on human sign-off. Every write is logged with the call that caused it.
Do you use our data to train models?
No. Store data is used to answer the request in front of it and nothing else.
Still stuck? Talk to an engineer.
Describe what is happening and what you expected instead. Include the store URL if you have one.