Skip to content
Orillaorilla.

Implementation and validation

This documentation describes repository code reviewed on October 17, 2026, with Orilla SDK 0.1.30. An implemented feature does not imply certification of capacity, every device, or every external provider.

Code and deployment

Section titled “Code and deployment”

The dashboard, landing page, and documentation deploy from the same GitHub main branch as three independent applications in Coolify. The operational record in docs/orilla-coolify.md identifies each release’s exact source commit and validation scope. English is the product language, and all three applications use the approved Orilla wave symbol and wordmark.

Earlier remote validation of 606d47f covered health, dashboard, sign-in, and API/SDK channel and volume queries, including the Data filters/traces, monitoring, comparison/insights, Usage, test mode, watermarks, HLS, clips, tracks, account, and notification increments. Release 191425f published the redesigned dashboard and public sites with browser navigation, search, and authentication checks. An earlier version also had an HTTPS workflow covering multipart/CORS, processing, HLS/ranges, iframe, and Usage. These checks are bounded evidence, rather than a remote rerun of all local functional tests for every feature.

The landing page and this documentation are independent static builds outside the platform’s Compose stack. The Orbicloud installation serves them at orilla-site.orbicloud.app and orilla-docs.orbicloud.app; other operators configure their own domains before building.

Distribution and integrations

Section titled “Distribution and integrations”

@orilla-video/sdk 0.1.31 and @orilla-video/player 0.1.2 were published publicly to npm on October 18, 2026, from source 7c7737b. These documentation patches replace implementation notes with installation and integration guides; their executable files match the first npm release. All 16 TypeScript examples compile against the packaged declarations. Registry README text, metadata, latest tags, archive hashes, external installation, SDK ESM exports and React server rendering were verified. The SDK requires Node.js 22 or later for server workflows; browser helpers use only temporary capabilities. Package publication is separate from API deployment and browser/device acceptance. The verification record is retained in docs/mux-research/evidence/npm-readme-release-20261018.json.

Password recovery and email notifications require operational SMTP. Slack/PagerDuty notifications have controlled local tests; configuration and delivery through external providers remain outstanding. MFA configuration and remote availability have been checked, but validation with a physical authenticator remains outstanding.

Outstanding limits

Section titled “Outstanding limits”
  • Environment admission quotas and shared media worker capacity are implemented and locally validated, awaiting deployment. The worker limits heavy pipelines per process and grants weighted queue turns. Local baselines cover 5-GiB multipart/resume and concurrent transport, plus four 30-second 1080p H.264/AAC videos with overlapping uploads and encoding under a two-CPU/2-GiB worker budget. A primary-source byte admission budget is also implemented and locally validated, awaiting migration and deployment. Unknown sources reserve available credit up to 5 GiB; downloads and canonical source growth use that allocation. Physical storage, derivative budgets, sustained load and production capacity remain outstanding. The combined run used forced worker teardown. Subsequent focused local checks validated worker exit 0, including a database wait of 20 seconds, after aligning the measurement runner with Compose’s existing grace of 45 seconds. Production shutdown acceptance remains outstanding.
  • Native asset processing observations and dashboard labels distinguish queued work, a current encoding lease and a lease awaiting recovery. Implemented and locally validated, awaiting deployment; these observations do not confirm an active encoder or recovery, percentage or ETA. Global queue and service observability remain outstanding.
  • Internal media-event and dispatch-receipt retention is implemented and locally validated, awaiting migration and deployment. It defaults to 90 days, can be disabled, and preserves pending dispatch, current recovery signals and durable cleanup tombstones. Expired direct-upload chunk digests now share this policy: pruning additionally requires confirmed object cleanup outside the window, preserves upload resources and bounds chunk rows per pass. Implemented and locally validated, awaiting migration/deployment. Native queue history has separate local verification, and durable recovery of five cleanup categories is implemented and locally validated, awaiting migration/deployment. Acknowledged obsolete MP4 attempts now have a local retention path requiring a finished writer and a later successful cleanup, with both confirmations outside the existing window; migration/deployment remain pending. Track and shared-audio-presentation attempts now reuse this retention path with explicit generation records, independent writers and protection for retained originals and active clip sources; migration/deployment remain pending. Static-download, master and image attempts now retain durable cleanup intent after uncertain writes and share this bounded retirement policy. All six media-attempt sweeps skip receipts with both confirmations while preserving periodic cleanup for unknown writers; matching partial pending indexes are included. Implemented and locally validated, awaiting migration/deployment. Daily Data CSV files now record explicit writer and cleanup confirmations, stop repeated S3 sweeps after both receipts and retire obsolete metadata under the same policy, preserving active references and download grace even after tenant/day deletion. Implemented and locally validated, awaiting migration/deployment; this increment follows the prepared 122dc07 candidate. Native primary upload cleanup now discovers ambiguous multipart creates and retains recurring exact-key cleanup after asset deletion, preserving known IDs privately and keeping unknown-writer intent. Locally validated, awaiting migration/deployment; the prepared122dc07candidate predates this change. Physical multipart reclamation, unknown-writer fencing/retirement, other upload metadata, job-recovery scenarios and compaction remain outstanding.
  • A read-only operator JSON report for the 13 video queues, broker heartbeats, pending media dispatch and notification schedules is implemented and locally validated, awaiting delivery. It distinguishes delayed work, ready backlog and expired active leases, with optional local worker progress. An optional private metrics exporter, persistent Prometheus history and local alert rules are also implemented and locally validated, awaiting operator configuration and deployment. Optional video/webhook worker endpoints now add their existing local progress predicate to that history; compiled processes and shutdown were checked locally. Stored storage inventory coverage and freshness now reuse existing scan records, with unknown versus measured-zero bytes and isolated observation failures; this is implemented and locally validated, awaiting updated observer grants and deployment. Worker endpoints also expose live capacity, available bytes and free inodes on their own temporary filesystem, with isolated failure and three additional local alert rules (17 total); this is locally validated and awaiting deployment. The observation does not enforce a quota or measure SeaweedFS volumes. The optional overlay also adds filtered native SeaweedFS objects-filesystem and selected service observations, bringing the current rules to 21. This is locally validated, awaiting an updated storage image and deployment; the native endpoint is unauthenticated on the two attached trusted networks, with no host publication or public gateway route. These observations do not certify fleet health, dependencies or job output; end-to-end S3 availability, other-volume/disk and dependency measurements, replica discovery, external alert routing and production sizing/acceptance remain outstanding. API readiness now coalesces its existing PostgreSQL/bucket checks under a 2.5-second total deadline with a one-second internal cache, destroys late acquired connections and returns uncached 503 on failure. Locally validated, awaiting deployment; liveness and worker checks retain their existing roles. The private exporter now observes that bounded API endpoint with a three-second HTTP/body deadline and fixed success/timestamp gauges, independently from database metrics collection. Two additional rules distinguish fresh failure from missing or stale observation (23 rules total); locally validated with compiled exporter and Prometheus, awaiting deployment. This observes one configured API endpoint and does not certify object GET/PUT or fleet health.
  • Backup schedules and database/volume copies are delegated to Coolify. Their configuration and restore drills still require operator validation. Redundancy, recovery and service observability remain outstanding.
  • Private download and master routes now recheck grants and live resource identity after storage waits and around durable receipt creation, before sending the body. Locally validated, awaiting deployment. Rejected requests destroy opened sources and discard new receipts; failed discard preserves pending coverage without confirming bytes. Whole/range/HEAD contracts are locally covered. Cancellation of already started streams, distributed/cache revocation and remote download/master acceptance remain outstanding.
  • A managed CDN with authorization and cache revocation is not included.
  • Rates, versioned costs, and public billing remain outstanding; Usage reports observed measurements.
  • Chapter controls have local Chromium, Firefox and Linux WebKit coverage, including keyboard navigation and pointer activation without changing play intent; delivery is pending. Image retries also have local coverage in these three engines: keyboard focus survives loading/failure, returns to the video on success when appropriate, and respects focus moved elsewhere. Delivery is pending. Broader keyboard/Firefox workflows, Safari, physical mobile devices, screen readers, AirPlay and Cast still need validation. General transport controls now have 30 additional local keyboard cases across Chromium, Firefox and Linux WebKit at desktop/narrow widths: play/pause, seeking, mute/status DOM, volume and speed-menu focus. The shared player now scrolls its submenu to keep the initial selected option and later keyboard choices visible, preserving existing controls and page position. Local validation only; delivery, actual screen-reader, broader keyboard and physical-device acceptance remain outstanding.
  • DRM, protected offline playback, HDR/premium profiles, and some advanced HLS topologies remain outstanding.
  • Continuous Data export, freely composed dashboards, and private experience scores remain outstanding.
  • Live and AI are deferred.

Analytics algorithms and Orilla extensions are identified as such. Route or external SDK compatibility does not establish equivalence with private algorithms or full parity. See formats and limits and deployment before operating your instance.