Welcome
Verentis for Developers
Build apps and execution engines that extend Verentis workspaces — and publish them to the marketplace. This is the guide for 3rd-party developers.
Welcome to the Verentis developer platform. These docs are for 3rd-party developers building apps and execution engines that extend Verentis workspaces and reach customers through the marketplace.
Looking for something else?
Using Verentis as a customer? See the user help site. Working on the Verentis platform source itself? That documentation is internal.
What you can build
UI extensions that render inside a workspace in a sandboxed iframe — viewers, editors, dashboards — resolved automatically by the type of file a user opens.
Code runtimes that execute files (e.g. .py) on the server in Docker or in the browser via
WebAssembly — on demand, on a schedule, or in response to file changes.
Both are manifest-driven extensions that share one envelope, one discovery model, one security model, and the same platform SDK. Learn the shared concepts once and apply them to either.
Start here
Understand the platform
Read The Verentis developer platform and Apps vs. execution engines to pick the right extension type.
Set up your environment
Follow Prerequisites & setup to get the tools and credentials you need.
Build your first extension
Work through the Quickstart to register a minimal app or engine in a workspace.
Find your way around
The extension model, manifests, the VFS, identities, tokens, and the MIME registry.
The app manifest, MIME resolution, the SDK bridge, consent, and local development.
The engine manifest, runtimes, the execution lifecycle, tools, triggers, and schedules.
OAuth, scopes, calling the API gateway, and working with files and nodes.
Package, version, and publish your extension to the marketplace.
Field-by-field reference for the app and engine manifests.