Reach a person,
not a queue.
Pick what you need and we route it to the inbox that owns it — with an honest reply target and the two or three details that get it answered on the first pass.
Tell us what it is.
We tell you where it goes.
Six inboxes, each owned by the people who can act. Choose one and the composer, the checklist and the shortcuts change with it.
The directory.
Bookmark this. Each address is a real inbox read by a person on that team, not a ticket bot.
How long you will wait,
and whether we are awake.
Every inbox has a target. The clocks show whether that target starts counting now or when the next region opens.
Remote-first. The team sits across these three windows, so most weekday hours someone is awake and reading.
Found something?
Tell us first.
Uplint holds the record and the routing for files that live in your buckets — which is exactly why we want to hear about a weakness before anyone else does. Write to security@uplint.dev, plain email is fine.
Component, steps, your read on impact. Send it to security@ before posting anywhere.
A human replies with a case reference and what happens next. No auto-responder.
You hear when it ships. If a customer was affected, they hear from us too.
Named in the dispatch that describes the fix, or kept anonymous. Your call.
Answered in advance.
Email is the fastest path — it lands with the engineer who can act on it, with your IDs and timestamps attached. Enterprise plans include a dedicated contact and agreed response times; ask sales@uplint.dev.
Open an issue on GitHub so the fix and the discussion stay public. If it involves credentials, a bucket or anything sensitive, use security@uplint.dev instead and we will move it into the open once it is safe.
Check the status page first — incidents are posted there with timelines, and you can subscribe for alerts. If the status page is green and your requests are failing, that is exactly what support@uplint.dev is for. Include a request ID.
Yes, through sales@uplint.dev. Say which documents procurement needs and the plan you are evaluating; the security page answers most questionnaires in advance.
We acknowledge every report within a day, keep you informed through the fix, and credit you publicly if you want that. Write to security@uplint.dev before disclosing anywhere else.
Remote-first, working across the Americas, Europe and Asia-Pacific windows above. There is no office to visit — the fastest way to meet the team is a call, which any inbox can set up.