Integrate through one governed boundary.

Customer-facing documentation explains how to connect, evaluate and operate cRUD Morph without exposing its private implementation.

Provider models

cRUD BYOP by default, with cRUD MIP also available.

Both operating choices use the same cRUD Morph product and customer APIs. Provider ownership changes who supplies credentials, receives the provider bill, approves capacity and takes responsibility for incidents involving the provider.

Hybrid is supported. A customer can combine media it owns with selected cRUD MIP components such as storage, CDN, transcoding, demonstration capacity or emergency fallback. Each managed component is scoped and approved separately. Commercial arrangements for cRUD Morph are discussed privately with The cRUD Company.

Connection and credentials

Connect a project, not a person’s provider login.

Ownership is explicit. Every provider connection is classified as cRUD BYOP or cRUD MIP. cRUD BYOP is the default and cannot silently become cRUD MIP.

Credentials belong to the approved project. A BYOP customer supplies dedicated credentials for the approved provider project. cRUD Morph does not require a provider dashboard password.

Credentials stay governed. Provider access is protected, limited to the approved work and subject to rotation or revocation. It is never exposed to another customer or placed in client-side content.

Environment separation matters. Development, staging and Production should use separate provider projects and credentials whenever the provider supports that model.

Provider support is confirmed per engagement. The providers, regions and capabilities that serve your product are confirmed during the technical engagement and remain within the same provider-neutral product boundary.

Capability access is confirmed per engagement. The available Morph capabilities, providers, regions, environments, limits and returned evidence are agreed for the customer’s integration. Public capability descriptions do not create a universal availability commitment.

Sandbox and environments

Validate the contract before spending on live media.

Hosted Sandbox. Explore the integration, expected responses, usage records and failure behaviour without connecting a provider or creating live provider consumption.

Staging owned by the customer. Testing with real media then uses the customer’s dedicated staging provider project, separate from Production.

Optional managed demonstration. cRUD may supply bounded, cRUD-managed demonstration capacity when it is explicitly approved.

Access. Sandbox access, API credentials, SDK distribution and the webhook reference are provided during the technical engagement, with limits and supported operations confirmed for your integration.

Production is separate. Sandbox credentials, demonstration capacity and test data do not imply Production capacity or a managed-service commitment.

Shared responsibility

The ownership model changes the provider boundary, not the product boundary.

Your application continues to define the experience and authorise media work. cRUD Morph applies policy and returns normalised state, outputs, health and usage records.

The customer owns
  • The customer experience
  • Brand and users
  • Engagement features
  • Commercial model and pricing
  • Its provider account, invoice and quotas in BYOP
cRUD Morph owns or coordinates
  • Application and provider connections within the agreed boundary
  • Session coordination and approved media policy
  • Media representation, composition and delivery
  • Recording, replay and continuity
  • Quality, usage, cost and assurance evidence
  • Provider operations for approved cRUD-managed components

Experience-control reference

What customers can expect from the extended product boundary.

cRUD Morph remains browser-first and provider-neutral. Customer-facing contracts expose approved capability, state and evidence while the private policy implementation and cRUD-owned credentials remain private.

01

Participant experience

Per-viewer state can reflect joining, healthy, constrained, audio priority, audio only, recovering or failed, with current cause and recovery evidence where available.

02

Continuity and recovery

Protect audio and authoritative state, avoid stale human video, return directly to live and keep recovered context separate from the current experience.

03

Privacy and retention

Raw telemetry is ephemeral by default. Diagnostic windows do not record participant audio or video, and durable incident evidence requires the applicable authority and policy.

04

Trust and evidence

Provenance describes origin and declared transformation history. Simulation, modelled results, provider reports, staging observations and Production certification remain separately labelled.

05

Cost and alternate paths

Cost follows safety, authority, privacy, continuity, freshness and contracted experience. Additional providers, telephone paths or cRUD-managed capacity require the applicable technical and commercial authorization.

06

Capability availability

The released environment, entitlement, supported provider, region and certified configuration determine which described capabilities are available to one customer integration.

Documentation map

What this page explains and what the engagement confirms.

This page explains the public product boundary. Interface references and customer-specific configuration are shared with the customer’s engineering team during the technical engagement.

01

Public product model

Product boundary, provider ownership, environments, shared responsibility and the connected capability families.

02

Interface references

Approved API, SDK and webhook guidance, request and event handling, usage limits and tested examples.

03

Engagement configuration

Capability availability, providers, regions, service limits, onboarding, evidence, retention and operating responsibility.

Questions

Evaluating a Morph integration

What can we validate before committing live media traffic?
Use the agreed Sandbox or staging path to check how your application authorises work, receives state and handles outputs. The technical engagement defines the validation scope before Production activation.
What determines which Morph capabilities our integration can use?
Availability depends on the released environment, entitlement, supported provider, region and certified configuration. Confirm the scope for your integration during the technical engagement.
How should a team prepare to activate the first Production scope?
Agree the baseline, success criteria, operating owners and rollback path. Validate the bounded scope outside the main customer path before making the activation decision.

Build adaptive media intelligence around your product.

Tell us what your product delivers, how your audience connects and which media responsibility you want to improve.