Thirty minutes of your time, the same of ours. We'll ask what you're shipping, what's getting in the way, and whether the runtime can help. No pitch deck. No slides. The agenda is your context.
Pick a slot that works for your week. We'll send a calendar invite with a video link, plus a short note on what we'd like to cover.
Open booking →Best for written threads, technical questions you'd rather think about, or anything that doesn't need a call. We reply within one working day.
Open mail client →Open issues, file pull requests, or thread up in Discussions. The engineering team triages directly. No customer-success layer.
Open repository →What does your agent do, what does it touch, what could go wrong. Your context teaches us faster than our slides could. We bring questions, not a pitch.
A real policy. A real audit log entry. A real blocked event from a customer's runtime. Whatever's relevant to your environment, on screen, no abstractions.
Concrete next steps, install instructions for your stack, a sample ruleset to start from, a Slack channel if you want one. Whatever moves the work forward.
If the embed below doesn't load (corporate proxies sometimes block it), the same calendar opens at the direct booking link.
If you've found a vulnerability in Lupid — the runtime, the gateway, the shield daemon, the policy engine — please send a note to security@lupid.ai. We acknowledge within twenty-four hours and follow a ninety-day coordinated-disclosure window. PGP key on request.