Everything the studio does is exposed over the same REST API the web app uses.
Create an API key in Workspace → Developer. Keys are scoped per workspace and can be restricted to ingest, render or read-only.
POST https://api.reelforge.app/v1/renders
Authorization: Bearer rf_live_...
Content-Type: application/json
{
"project_id": "prj_8f21c",
"prompt": "24s product story, calm pace, teal grade, Dutch captions",
"outputs": ["master", "9:16", "1:1"],
"resolution": "1080p"
}
Renders are asynchronous; poll the job or subscribe to the render.completed webhook.
GET https://api.reelforge.app/v1/renders/rnd_2c9a1
→ 200 {
"id": "rnd_2c9a1", "state": "rendering", "progress": 0.62,
"eta_seconds": 41, "credits_reserved": 24
}
60 requests/minute on Studio, 600 on Enterprise. Render concurrency is plan-based: 1, 4, 12.
1. Accounts. You are responsible for activity under your workspace and for keeping credentials secure. Workspaces must be operated by the entity that registered them.
2. Credits. Credits are prepaid and non-refundable except where required by law. Paid-plan credits roll over for one billing cycle. Failed renders are refunded automatically.
3. Content. You retain all rights to the media you upload and to the renders you produce. You grant Reelforge a limited licence to process that media for the purpose of delivering the service.
4. Acceptable use. No unlawful content, no impersonation of real people without consent, no circumvention of output watermarks on the free plan, no resale of raw render capacity.
5. Availability. Enterprise plans carry a 99.9% monthly uptime commitment; other plans are provided as-is with best-effort availability.
We process account data (name, email, billing details), usage data (render minutes, project metadata) and the media you upload. Legal bases: contract performance for the service, legitimate interest for security and product analytics, consent for marketing email.
Processors: Hetzner (hosting, EU), Stripe (payments), Postmark (transactional email), Sentry (error tracking, EU region). Sub-processor list is published on request and updated 30 days before a change.
Data subject requests: privacy@reelforge.app. Response within 30 days.
A DPA based on the EU Standard Contractual Clauses is available for all paid plans and incorporated by reference into the Enterprise agreement. Rendering and storage stay inside the EEA unless the customer explicitly enables US processing.
Strictly necessary: session, CSRF and load-balancer affinity cookies. Analytics: self-hosted privacy-friendly counters, no third-party trackers, no cross-site identifiers. No advertising cookies are used anywhere in the product.
Current status: all systems operational. Incident history and
subscribed notifications are available at status.reelforge.app.