PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
Feature scope - proposed scope

HeyGen Clone Features

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Build scopeConfirm servicesDefine the features and exclusions
Delivery planAgree milestonesNo fixed launch duration implied
Source rightsWritten termsCheck licences and handover
OperationsTest before launchAgree acceptance and support
01 / Scope areas

Scope areas for this kind of build

The areas below are condensed from our earlier product specification for this category. They describe proposed scope we can build for you, not a finished product for sale, and no live system is implied. The exact list is agreed in writing for your project before any build starts.

02 / Feature Set by Role

Feature Set by Role

Four surfaces sharing one workspace model. Every project, asset, template, webhook and subscription hangs off a workspace, which is what makes multi-brand and multi-client operation possible without separate installs.

User & Creator

  • The production loop, from a blank script to a finished export.
  • Script drafting with full version history
  • Avatar and voice assignment per project
  • Queue-backed generation with real status tracking rather than a spinner

Manager

  • Running a team's output rather than making individual videos.
  • Workspace-scoped visibility across projects and assets
  • Team membership and role assignment inside the workspace
  • Template curation so brand output stays consistent

Platform Admin

  • The eighteen-tab command center covering the whole deployment.
  • Workspaces, users, projects, videos and assets
  • Session management and platform configuration
  • Integration status across connected services
03 / Technology

The Technology Behind the Features

React and TypeScript on the front end, an Express API, PostgreSQL with Drizzle, and Redis behind the job queues. Generation, translation and export each run as their own queue-backed pipeline with Redis workers and an inline fallback, which is what lets rendering survive campaign-week spikes instead of timing out under them. The eight UI languages carry 156 translation keys per locale across English, Spanish, French, German, Hindi, Arabic, Chinese and Portuguese, switchable at runtime without a page reload.

04 / How It Works

How It Works, End to End

Video generation is a queue problem dressed as a creative tool. Here is the path from workspace to measured output, and why each stage is separated the way it is.

Onboard and scope the workspace

  • A user signs up, a workspace is created, and they become its owner. Everything downstream hangs off that tenancy boundary - which is why the workspace is created first rather than derived later.

Author the script

  • Projects hold creative intent; scripts hold the words. Every revision is snapshotted rather than overwritten, so editorial history survives - which matters the first time a client asks to go back two versions.

Localize

  • Translation is its own entity with its own worker, so a localized version has independent status and does not disturb the source. A failed Spanish render never takes the English one with it.

Export and distribute

  • Output packaging is a governed stage - what you can export depends on the plan you are on, and that is enforced at the export service rather than hidden in the interface.

Measure

  • Analytics close the loop, which is what turns a production tool into something a marketing lead will defend in a budget review. A tool nobody can justify does not get renewed.
05 / Why these

Every Feature Earns Its Place

A feature list tells you what exists. This tells you what each one is worth to an operator, and what it costs you not to have it.

06 / Boundaries we state

Boundaries we state in writing for your build

The workspace model, the generation pipeline, localization and the plan-gating layer are complete. The list below is what is not, and one item is a hardening step we would want any serious deployment to take.

07 / See exactly what you

See exactly what you are getting - before you commit

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by HeyGen.

HeyGen Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to HeyGen, and how clients search for it.

08 / More pages

More pages on this build

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by HeyGen.
HeyGen Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to HeyGen, and how clients search for it.

09 / Next step

Discuss your scope by message

Tell us what you want to launch and where. We reply by email with a scoped proposal - no calls required, no phone numbers collected.

PREVIEW ONLY - nothing you enter is submitted to or stored by Omnistu. The compose button tries to copy your scope text and open your own email app; if the copy does not work, the text appears below the button so you can copy it yourself. Nothing is sent until you press send in your own email app.
Email the team instead