For business
Let AI agents use your customers' details without holding them.
If you build agents, connect them so your clients' details can go to websites through our site kit without passing through your workflows. If you run a website, receive details from agents with a signed receipt instead of a copy in the agent's hands.
Sealed before it reaches us — and the keys stay with you, not us.
For people who build agents
Connect any agent that can send an HTTP request (the MCP server isn't available to download during the beta). When a website receives your clients' details through our site kit, they stay out of your workflows and your logs.
Request free beta accessFor websites
Receive details from AI agents sealed for your site, while the agent carries a one-time token. A small server-side kit checks each request and gives you a signed receipt.
Talk to us- You hold the keys — values reach us only sealed
- Standard cryptography — never hand-rolled
- Every site delivery needs a passkey approval
What you can do today
Agents use the details. They don't need to hold them.
One sealed core underneath, for the agents you build and the websites that receive.
See it step by step
Your agent asks. You approve. The site receives.
Your details travel from your phone to the website sealed so only that site can open them. The agent carries a one-time token, never the values.
Deployment
Where it runs today
Honest about what is ready and what is not.
Hosted by us — beta
Today Hesimesi runs as a hosted beta. Use it to test with sample data; values are sealed before they reach us, and during the beta we can't promise to keep what is stored.
Your own cloud or servers — not yet
Not offered yet. If you need it, tell us your timeline and we'll talk it through.
Security & trust
Built to be checked
Standard cryptography, nothing hand-rolled, and no outside audit yet. Here is what your security team can check today.
Check files yourself
Check them with our command-line tool: a passphrase-locked .rbx opens in the browser and in the CLI alike. Time-locked files open in the browser only.
Standard cryptography, nothing hand-rolled
XChaCha20-Poly1305 · Argon2id · HKDF-SHA-256 · Shamir. Hesimesi has not had an outside audit yet.
Site deliveries are on the record
A site delivery can't go ahead without its entry in the owner's activity log. During the beta, that log is not yet protected against someone who can write to our database.
Contact
You'll reach me directly
Tell me what you're building: an agent that needs your clients' details, or a website that receives details from agents. I read every message myself: we're early, and I'd rather answer you myself than pretend otherwise.
We keep what you send and your IP address for 12 months, to reply and to stop abuse — no trackers. How we handle your data
Or email us directly: support@hesimesi.com
Questions
What teams actually ask.
Not the contents. Files and field values are sealed on your device before they reach us, and, as long as the code our website sends to your browser is honest (that code does the sealing), we don't receive the key that opens them, so neither we nor a breach of our storage can open them, except a file you lock only to a date and keep with us: once that date passes, anyone holding it can open it. What we keep readable, we can read and a breach would expose: email addresses, file and field names, labels and destination addresses, the sign-in log with IP addresses, the activity log and contact-form messages. Field names stay readable so agents can ask for them. Recovery is Shamir-split across people you designate, so even that path doesn't involve us.
You control recovery. When you seal something, you can split the key using Shamir's Secret Sharing and give shares to designated trustees. Any threshold of those trustees — say 3 of 5 — can recover access together, with no single person (and no one at Hesimesi) holding enough alone, so one trustee leaving doesn't lock you out. Accounts belong to one person today; shared team vaults are not offered yet.
During the beta, agents connect over plain HTTP (the MCP server isn't available to download yet), and our tools give them the names of the details, not the values. When a website receives details through our site kit, the agent carries a one-time token, not the values, provided the owner approves with a passkey on a device the agent doesn't use; the site receives them sealed, with a signed receipt. Browser fills follow the owner's policies (deny, ask, or allow) and put the value in a page the agent may be able to read.
The engine uses standard cryptography (XChaCha20-Poly1305, Argon2id, HKDF-SHA-256, Shamir) and nothing hand-rolled. Hesimesi has not had an outside security audit yet, and neither has the post-quantum library that seals site deliveries. Your security team can check its behavior with our command-line tool and review the audit trail. We do not currently hold SOC 2 or ISO 27001 certifications — if that is a hard requirement, talk to us about your timeline.
Today, a hosted beta that we run, for testing with sample data. Running it in your own cloud or on your own servers is not offered yet — talk to us about your timeline.
During the beta, on our hosted service. Values are sealed before they reach us, so we hold them only as ciphertext we can't open; your email, field names, labels and the activity log are stored there readable. During the beta we can't promise to keep any of it.
Not today. You sign in with an email and password, a one-time sign-in link sent to your email, or a passkey. If your company needs SSO or SCIM, tell us your identity provider and timeline.