Skip to content
Contact

Talk to us.

Three routes, kept apart on purpose: sales, support, and security. Each one goes somewhere different, and each one is answered by a person rather than a ticket robot — because there is no ticket robot.

Everything about plans, credits and limits is documented on this site. If your question is “which tier do I need”, the calculator answers it in a minute.

Pick the right door

Sales

For tier recommendations, footage-volume questions, and anything a business needs before it signs up. If you want to see the product working on your own footage, book a twenty-minute demo instead of writing — it is faster and you leave with an edit.

If you already know roughly what you need, the fastest answer is the credit calculator: it takes your hours per month and returns a tier, a price and the minutes included. The pricing page then shows the exact limits of that tier.

Support

For a video that failed, credits that look wrong, a bill you did not expect, or anything the product did that you cannot explain. Use the form below — it asks for the video or project first, because that is the only way to look at the real job report.

Before you write, the how it works page names every stage and every error state, and trust covers what Studio refuses to do. Half of all support questions are answered on those two pages.

Response times by plan are listed beside the form. They are the intent, not a promise.

Security

For vulnerability reports and data-handling questions. Please do not open a support ticket for a security finding — use the disclosure route below so it reaches the person who can fix it.

What Studio stores, and for how long, is written down in how we prove it.

Go to the disclosure panel
Support

Tell us which video

Four fields. The video or project name is the one that matters — it is how the job report, its decisions and its error log get found.

No attachments on this form yet. If a file is needed, we will ask for it in the reply — there is no inbound email to send it to.

Not built yet — this form would only log the request
The backend has no email sending at all: no outbound mail, no inbound mailbox, no auto-reply, no job reports by email. Pressing send here would write a row and stop. You would then have to be told out of band that it arrived, and any reply you wrote back would have nowhere to land. What is already there to build on: the status page reads GET /studio/api/health, which already returns the version, lane count, upload chunk size and retention window — so a real support workflow would not start from nothing.
Response times

What each plan gets

PlanSupportTypical reply
Free CommunityNo guaranteed reply
Creator EmailWithin 2 business days
Pro EmailBy the next business day
Studio Business Priority, plus an onboarding callAhead of the other tiers

These times are the intent, not a contractual commitment. Studio has no SLA. There is no uptime guarantee, no credited-back time, and no 24-hour desk — the times above are what the tier is designed to deliver, written down so you can hold us to them in a conversation rather than in a contract.

Whether the server is up right now is a separate question, answered by the status page. Plan names and prices: pricing · what a minute costs: credits.

Security

Reporting a vulnerability

Write to security@example.invalid and put “security” in the subject line. That address is a placeholder. No security mailbox exists yet, and Studio sends and receives no email, so this route is designed rather than live — the real address would be published here and nowhere else, and it would be monitored by the person who can ship a fix.

What to include
  • What you found, and the exact steps that reproduce it.
  • The URL or route involved — for example /studio/api/jobs/<jid>.
  • What an attacker gains: footage, an account, credits, or nothing.
  • Whether you have already told anyone else.
  • A way to reach you, and whether you want to be named.
What happens next
1 We acknowledge your report by hand
2 We reproduce it and investigate with you in the loop
3 We tell you when it is fixed, and what changed before we write about it

No bug bounty exists, and no payment is offered for reports. Please do not test against other people's footage or accounts — every account here is somebody's real video.

You may not need to write to anyone.

The first 30 minutes are free, every decision the Studio makes is readable, and revisions cost nothing. Most questions are answered by running one real video through it.

Already have an account? Sign in.