Klippy

Before you buy

Use this checklist to confirm Editor Starter is the right fit, understand what is and is not included, and plan the evaluation work needed before purchasing a commercial license.

Prerequisites

  • Team skills: experience with React, TypeScript, and Redux Toolkit. Familiarity with FFmpeg concepts helps when tuning exports.
  • Runtime: Node 18–20 LTS, pnpm/npm, and a modern browser with IndexedDB and SharedArrayBuffer support for best performance.
  • Infrastructure: ability to host a Next.js 15 application (Vercel, Cloudflare, custom Node) and configure HTTPS, headers, and environment variables.
  • Security reviews: willingness to manage your own deployment, storage, and API keys — Klippy does not host your data.

What you receive

  • Full source code for the production Klippy editor (Next.js project, timeline components, export engines, Redux store).
  • Documentation at /docs/editor-starter covering setup, architecture, backend routes, persistence, and production readiness.
  • Utility scripts, IndexedDB storage manager, captioning/transcription integrations, and testing helpers.
  • Access to updates and bug fixes delivered through the private repository (details outlined on the Buy page).

Know the boundaries

Editor Starter accelerates private, single-player editing workflows. It does not include:

  • Real-time multi-user collaboration, cloud project sync, or hosted backend services.
  • Advanced NLE features like HDR grading, HEVC/AV1 export, motion tracking, or keyframe graph editors (see Features not included).
  • Managed Remotion Lambda deployments — guidance is provided, implementation is up to you.
  • Per-seat desktop apps; you host the web app and control distribution.

Security & compliance considerations

  • Media stays client-side in IndexedDB. Your deployment owns API keys for stock media, AI, and transcription proxies.
  • Middleware enforces origin allowlists, CSP, Permissions-Policy, and rate limits; you must configure NEXT_PUBLIC_SITE_URL and ALLOWED_ORIGINS correctly.
  • FFmpeg WASM multi-threading requires COOP/COEP headers. These are included but depend on your hosting platform honoring them.
  • 3rd-party content (Pexels, Tenor, Meme) and optional services (Sentry, PostHog) follow their own terms. Confirm usage fits your legal requirements.

Pre-purchase checklist

  1. Evaluate the open documentation and demo script to understand feature depth.
  2. Decide how you will integrate storage, branding, auth, and analytics (outside the scope of the starter).
  3. Document required customizations, missing codecs, or design changes so we can confirm feasibility.
  4. Plan ownership: who will maintain the fork, review upstream updates, and support your users.
  5. Prepare any vendor or procurement questionnaires — we can supply technical and security answers after initial scoping.

Need hands-on help?

We can assist with guided evaluations, integration planning, or bespoke features. Share details via the contact form — include your timeline, team size, target customers, and any compliance constraints.