Isolated Embed Runtime

external content, internal control.

Run third-party embeds. Keep your trust boundary.

aetherframe isolates embeds in capsules. server policy decides allow or block.

tokens identify. policy enforces.

choose an explanatory scenario

trigger · a supported url contains a recognized tracking query key

allow

The embed ID points to a valid record.

dev: Identity is accepted, policy flow continues.

recognized keys are removed; the provider still receives the viewer request when loaded

your pageyourdomain.com

aef.to/Ab3xY9 · the link on this page

story

professional emotion, not noise

three things a publisher feels once the boundary is real.

your page stays yours: Embeds can be rich.; Trust stays in your control.
publish fast, panic less: Teams ship media quickly.; Risk is checked before render.
bounded resize without visual collapse: Content still looks alive.; Layout stays stable under load.

containment shape

pick a layer. the page shows where it lives and what it can reach.

your trust zone

your origin, your cookies, your DOM. nothing below reaches it.

your pageyourdomain.com

aef.to/Ab3xY9 · the shell on aef.to

audience mode

choose your lens. the needs on the left are met by the signals on the right.

ship fast. see the boundary.

needs: Drop in rich embeds; Normalize known tracking keys; Keep page flow smooth; Disclose provider contact
signals: Origin checks gate access; Tracking params stripped; Resize behavior bounded; Compatibility is explicit

safety readout

inspect a signal. three probes try the line; the line holds.

always-on control

Unauthorized origins can be denied before render.

dev: Request admission checks host policy every time.