Contact · founder-led
Contact
Galdo is founder-led. There's no ticket queue and no chatbot in front of a human. You're writing to the person who builds the thing.
The general address is shah@mnemohq.com. It reaches a monitored mailbox and it's the right choice when you're not sure which of the addresses below applies. Expect a reply within one business day. Galdo runs on Pakistan Standard Time (UTC+5), so a message sent late in the US afternoon usually gets an answer the following morning your time.
Book a demo
Email shah@mnemohq.com with a line about your team, the tools you work in, and two or three times that suit you. You'll hear back within one business day to set a time. The call is with the founder, and it's built around your use case and your questions, including security ones.
What to write about
- Product support — a connector that stopped syncing, an answer whose source looks wrong, an API call behaving unexpectedly, quota or rate-limit questions, SDK bugs. Include your workspace ID and, where you have one, the request ID from the response, so the failure can be traced end to end instead of guessed at. Email shah@mnemohq.com.
- Sales and evaluation — rolling Galdo out to a team, plans and pricing, volume commitments, security questionnaires, DPAs, procurement paperwork, or a walkthrough of the architecture with your team. Email sales@mnemohq.com.
- Security disclosure — send vulnerability reports to security@mnemohq.com. Coordinated disclosure is welcome and reports are acknowledged within one business day. Please don't open a public issue before we've had a chance to respond.
- Privacy and data requests — access, export, correction, and deletion requests go to privacy@mnemohq.com, which is also the Data Protection Officer address. Contract and legal questions go to legal@mnemohq.com.
- Partnerships and integrations — if you're an agency that sets up company memory and agents for clients, or you build a framework, agent platform, or tool that wants a first-class Galdo integration, write to shah@mnemohq.com with a sentence on what your clients or users would gain. Existing integration work is listed on the integrations and partners pages.
Elsewhere
- X: https://x.com/shhahhussain — release notes, benchmark writeups, and the fastest route to a short answer.
- GitHub: https://github.com/shhahhussain — the SDKs, the MCP server, and the open parts of the stack.
Before you write
Three places answer most incoming questions faster than an email round trip: the API documentation for endpoint behaviour and authentication, the benchmarks page for the full per-category LongMemEval breakdown and how to reproduce it, and the trust and security page for encryption, hosting, and compliance status. If the answer isn't in one of those, it belongs in an email. And if it should have been, say so. That's a documentation bug worth fixing.