Turn raw videos into an editable reverse script
Upload any number of videos, then manage scene split, bbox, entity clusters, reverse script, and AI edit plans in one workspace.
Phase one focuses on a high-fidelity frontend workspace before real models and jobs.
from 99+ happy users
Built on a practical production stack
What this starter gives you
A beginner-friendly Cloudflare full-stack template with clear domain boundaries, reusable UI building blocks, and working SaaS defaults.
- Clear ArchitectureBusiness logic flows through app, services, models, and Cloudflare bindings in a way new contributors can follow.
- Practical SaaS DefaultsAuthentication, payments, credits, orders, referrals, and blog flows are already shaped like a real product.
- Cloudflare Runtime ReadyUse D1 for relational data, R2 for assets, and preview the runtime locally with Wrangler.
Why use this template
It is opinionated enough to help beginners move, but still modular enough to grow into a product.
How to use it
Treat this project as a starter, not a locked product:
Key features
Enough infrastructure to start shipping, without hiding how the app works.
Next.js App Router
Structured routes, server actions, metadata, and i18n-ready pages.
Auth and billing
Auth.js plus Stripe-backed order flows and console pages.
D1 and R2
Relational data in D1 and file or generated assets in R2.
Cloudflare preview
Preview runtime behavior locally with Wrangler before deploying.
Analytics hooks
OpenPanel and page instrumentation are already wired in as starter pieces.
Provider-based AI routes
Swap model vendors without rebuilding the whole app boundary.
What you can build
Made to be edited
This starter is meant to be reshaped into your own product.
Main domains
6+
Starter business flows
Cloudflare services
2
D1 and R2 ready
Minutes to first run
10
after env setup
Example pricing
Sample plans to help you start with billing, credits, and account upgrades. Replace these with your own product pricing.
Starter
A lightweight plan for testing the basic flow.
Includes
- 100 credits
- Basic account access
- Example checkout flow
- D1 order records
- R2 asset support
- API key support
- i18n-ready UI
Starter placeholder. Replace with your own SKU.
Standard
A balanced plan for the default SaaS monetization flow.
Everything in Starter, plus
- 200 credits
- Longer validity window
- Referral-ready order flow
- Admin order management
- Analytics hooks
- Legal page placeholders
- Template release checklist
Useful default for your first paid tier.
Premium
A higher tier for referrals, more credits, or team features.
Everything in Standard, plus
- 300 credits
- Long-term access
- Referral program support
- Admin console access
- Priority support placeholder
- Richer upgrade path
- Space for enterprise rules
Another example tier. Replace freely.
Starter goals
These are example outcomes, not customer quotes. Replace them before launch.
Cleaner first launch
Architecture
A new contributor can find the app, service, model, and storage layers without guessing where business logic lives.
Less glue code
Cloudflare
D1 and R2 are already wired into the starter, so you can spend time on product rules instead of redoing storage setup.
Safer edits
Beginners
The UI and feature folders are split so beginners can make content changes without touching every shared component.
Real SaaS flows
Billing
Orders, credits, referrals, and API keys already exist as starter domains instead of being left as TODO comments.
Template, not trap
Ownership
The starter is meant to be renamed, rewritten, and stripped down so your repo becomes your own product quickly.
Launch-ready defaults
Ops
Lint, build, and local Cloudflare preview are already part of the expected workflow.
Frequently asked questions
Replace these starter answers with product-specific support content when you publish.
Is this meant to be a finished product?
No. It is a starter with working SaaS structure, Cloudflare runtime wiring, and example business flows that you should customize.
Do I have to use Cloudflare?
The current architecture is Cloudflare-first. The data and asset layers are shaped around D1 and R2.
Can I change the pricing model?
Yes. The current plans are examples for billing and credits. Replace amounts, durations, features, and upgrade logic with your own rules.
Can I remove domains I do not need?
Yes. The project is organized by feature so you can remove or replace business areas without tearing up the whole app.
What should I replace before launch?
Branding, pricing, legal pages, support links, placeholder emails, screenshots, and any sample business copy.
Is the legal copy production-ready?
No. The legal pages are starter placeholders and should be reviewed and replaced with your own terms and policy.
Start from the starter, then make it yours
Use the current structure to launch faster, but replace the copy, links, pricing, and legal details before shipping.