Skip to main content
A trust tier is the security class that determines how much code a package runs and how much the host trusts it. In evoX every package falls into a tier; the tier determines what it can load, how it runs and whether it can go to the public Market.
Everything you upload to the public Market through the web is T0. The T1/T2/T3 executable flows are for the Developer SDK and the host side; public executable upload is currently closed with PLUGIN_UPLOAD_NOT_READY.

​
T0 — Data packs

The most common tier and the only one open to the public. It runs no code; it carries only data and assets.
  • What it contains: Ready profiles, action packs (native behavior presets), icon packs, sound packs.
  • How it works: The host reads the pack and applies its content in its own native runtime. No executable JS/native/script runs in the pack.
  • Sandbox boundary: Not needed — there is no user code being run. Security is provided by static scanning (secret leakage, magic-byte, active SVG, forbidden extension, path traversal).
  • Capability: None. Only the native action/integration requirements declared in the manifest.
  • Public status: ✅ Open. Sign in → upload → scan → moderation → Market. No separate publisher application is needed.
  • How to publish: Publish your own pack (export from the desktop → sign in → upload).
If you are sharing a profile, icon set or sound collection, your tier is T0 and you can publish today.

​
T1 — Local development (trusted)

The tier you use while developing plugins with the Developer SDK. T1 is trusted local Node code and is not a sandbox.
  • What it contains: A developer plugin with manifest.json + a runtime entry file (.mjs).
  • How it works: The host runs the plugin in a separate Node child process; it provides bounded logs, heartbeat, a restart budget and a stable provider identity. It does not block normal Node access (fs, network, process).
  • Sandbox boundary: None. So run only a source you have reviewed and trust yourself. T1 is for session-only dev or explicitly trusted managed local.
  • Capability: Declared in the manifest, but the host gives the trusted process full access; the real protection is the “trust the source” decision.
  • Public status: ⛔ Does not go to the public Market. It is a local development/test tier.
  • Start: Run the checked-in trusted-counter example with the T1 quickstart.

​
T2 — Public sandboxed target

The tier targeted for public distribution. T2 is default-deny: only declared ∩ granted capability calls reach the host broker.
  • What it contains: A browser-compatible, signed plugin bundle.
  • How it works: Runs inside a sandboxed Chromium Worker. There is no Node, DOM, direct network, filesystem or process access. The only way to the outside world is the host broker.
  • Sandbox boundary: Bound to the exact bundle digest; uses scan/signature/revocation start gates and a host-assigned identity. The plugin cannot change its own identity or permission set.
  • Capability: Default-deny. The plugin declares its needs in the manifest; the user/host grants them; only the declared ∩ granted intersection works. Raw credentials never enter the plugin’s request/response.
  • Public status: 🟡 Foundation exists, public upload closed. It does not open until the build, dynamic scan, signing, revocation and Market installer chain is complete.
  • Concepts: Capability model and manifest.
Even if a source is written with T2 APIs, it is not considered public-ready until the build, dynamic scan, signing, revocation and Market installer chain is complete.

​
T3 — EXE, DLL or driver

The highest-risk tier, carrying native executables.
  • What it contains: Native artifacts such as .exe, .dll or drivers.
  • How it works: Runs at the operating system level; it cannot be limited by a sandbox.
  • Public status: ⛔ Not self-service. Handled only through a special Wraith security/release review.

​
Which tier is right for me?

T0. You don’t need to write code; export from the desktop and publish on the web. Open today.
T1. Develop with the Developer SDK and run it in a separate process. It is not a sandbox; run only a source you trust. It does not go public.
Target T2: default-deny capability, sandboxed worker. The foundation is ready but public upload is still closed — follow the status on the Distribution status page.
T3. Not self-service; a Wraith security/release review is required.