Skip to main content

Embedding & white-label

Enterprise licensees can embed the full Corte editing surface — media library, preview, inspector, timeline, agent panel, and export — inside their own product, under their own brand. The embed is a single React component with none of the Corte SaaS shell: no home screen, no auth forms, no billing UI, no settings chrome. Your app stays in charge of all of that.

The minimal embed​

import { EliEditor } from 'eli/editor'

export function App() {
  return <EliEditor theme="light" />
}

That alone is a fully working local editor — import media, edit, export. AI features stay hidden (or show connect prompts) until you provide services.

Bring your own auth, billing, and AI​

Everything account-shaped is injected through an EditorServices implementation. The editor never renders sign-in or paywall UI — when a user hits a wall, it calls your requestSignIn / requestUpgrade hooks and your app takes over:

import { EliEditor, type EditorServices } from 'eli/editor'

const services: Partial<EditorServices> = {
  account: {
    isSignedIn: () => myAuth.isSignedIn,
    remainingCredits: () => myEntitlements.videoAiRemaining,
    requestSignIn: () => myAuth.openLogin(),
    requestUpgrade: (reason) => myBilling.openPaywall(reason),
    // …
  },
  agentTransport: {
    available: () => true,
    // Any endpoint that accepts an Anthropic Messages request and returns SSE.
    stream: (body, signal) => fetch('https://ai.yourco.com/agent', { /* … */ }),
  },
  features: { agent: true, generation: true, transcription: true, export: true },
  branding: { productName: 'YourCut' },
}

<EliEditor services={services} />

Every service is optional — feature flags hide whole surfaces (agent, generation, transcription, export) per tenant.

Running on the Corte cloud instead? Skip writing services entirely:

import { EliEditor, createEliBackendServices } from 'eli/editor'

<EliEditor services={createEliBackendServices({ url: 'https://api.corte.so' })} />

Tenant resolution — branding, feature flags, model catalog, credit metering — then follows the backend's tenant mapping.

Make it yours​

  • Theming. The editor is styled entirely with CSS custom properties — every color, radius, and shadow token can be overridden per tenant, in light and dark. Point --accent at your brand color and the whole surface follows.
  • Tenant packs. A tenant pack is a plugin that applies branding (product name, logo, theme overrides) and contributes content: your own project templates, a branded stock library, extra models, even custom agent tools. Packs are selected per tenant at boot and revert cleanly on deactivate.
  • Templates + stock. Because templates and library assets are pure data, a white-label pack can ship a complete branded starting experience — formats, title cards, and hero footage — with no custom code.

Licensing​

Embedding and white-label are enterprise features, licensed with volume credits and support. Talk to us about your use case — or start with the pitch on corte.so.