Getting started
The Verentis developer platform
How Verentis lets you extend workspaces with apps and execution engines, and how those extensions reach customers through the marketplace.
Verentis is a multi-tenant platform for storing, organising and working with content inside workspaces. As a developer, you extend what a workspace can do by shipping two kinds of extension:
- Apps — UI you render inside the workspace (viewers, editors, dashboards).
- Execution engines — code runtimes that process files (run a
.py, render a diagram, transform data).
Customers discover, install and govern your extensions; you focus on the experience and the code.
The big picture
You publish an extension
You describe your extension in a manifest — a small YAML file with a Kubernetes-style envelope
(api-version, kind, metadata, spec). Apps use kind: Application; engines use
kind: ExecutionEngine.
A workspace installs it
Installing an extension means placing its manifest in the workspace's virtual file system (VFS) — either directly, or with one click from the marketplace. The VFS is the source of truth: add the manifest to install, remove it to uninstall.
Verentis wires it up
The platform registers your manifest, resolves which extension handles which file type, and runs your app in a sandboxed iframe or your engine in a sandboxed runtime — handing it scoped tokens so it can call the platform on the user's behalf.
Why one model for two extension types
Apps and engines deliberately share the same foundations, so you only learn them once:
Same api-version / kind / metadata / spec shape; only the kind and the spec details differ.
Both are discovered from manifests in the workspace VFS (the global /applications/ folder or
co-located with content).
Both receive short-lived, scoped tokens and declare the permissions they need up front.
Both talk to the platform through a Verentis SDK (TypeScript for apps in the browser; language SDKs for engines).
What's stable vs. evolving
The Verentis extension platform is built in layers. The app and engine runtimes and their manifests are implemented today, and the marketplace publishing flow (packaging, signing, moderation and installation) is live — see Publishing. Some surfaces — notably AI agents — are still being rolled out and are flagged as coming soon in these docs.
Building toward the full vision
These docs describe the complete developer experience. Where a capability is still landing, you'll see a Soon badge or a coming-soon banner — but the manifests and APIs you build against are designed to be forward-compatible.