Core concepts

On top of its editors to build endpoints, scripts and flows, Orvanta comes with a set of features.

Orvanta has three flow authoring models, all sharing one execution engine, the same permissions, and the same runs UI: DAG Flow, the node-based canvas and the most mature of the three; BPMN Flow, standards-based process modelling with BPMN 2.0 notation; and Code Flow, orchestration written directly in Python or TypeScript (a beta capability, off by default since 6.2.0). They’re different authoring surfaces over the same kind of artifact, not three separate products — see Flows as artifacts.

Triggers

Schedules. Scheduling allows you to define schedules for Scripts and Flows, automatically running them at set frequencies.
Webhooks. Trigger scripts and flows from webhooks.
Emails. Scripts and flows can be triggered by email messages sent to a specific email address.
Orvanta MCP. Connect LLMs to Orvanta using the Model Context Protocol.
Custom HTTP routes. Trigger scripts and flows from custom HTTP routes.
Websocket. Trigger scripts and flows from WebSocket servers.
Postgres. Trigger scripts and flows from postgres database servers.
Kafka. Trigger scripts and flows from Kafka topics.
NATS. Trigger scripts and flows from NATS subjects.
SQS. Trigger scripts and flows from Amazon SQS.
MQTT. Trigger scripts and flows from MQTT broker.
GCP. Trigger scripts and flows from Google Cloud Pub/Sub messages.
Azure Event Grid. Trigger scripts and flows from Azure Event Grid events.
Native triggers. Trigger scripts and flows from Nextcloud, Google Drive, and Google Calendar events.

Orvanta features

Architecture. Schema of Orvanta architecture.
Auto-generated UIs. Orvanta creates auto-generated input forms for running and testing scripts and flows, based on their parameters.
JSON schema and parsing. JSON Schemas are used for defining the input specification for scripts and flows, and specifying connection types.
Instant preview & testing. Orvanta allows users to see and test what they are building directly from the editor, even before deployment.
Rich display rendering. The result renderer in Orvanta supports rich display rendering, allowing you to customize the display format of your results.
Dependency management & imports. Orvanta resolves dependencies straight from a script’s imports and generates a lockfile at deploy time, so there’s no separate manifest file to keep in sync by hand.
Workspace dependencies. Centralized dependency management at the workspace level for shared dependency files across scripts.
Code Flow. Write distributed workflows in TypeScript or Python with checkpoint-based orchestration, parallel execution, and fault tolerance.
BPMN Flow. Model processes with BPMN 2.0 notation and drive branching with DMN decision tables — standards-based orchestration alongside DAG Flow and Code Flow.
Draft and deploy. Develop and cooperate in a structured way.
Persistent storage & databases. Ensure that your data is safely stored and easily accessible whenever required.
Object storage in Orvanta. Orvanta comes with native integrations with S3, Azure Blob, AWS OIDC and Google Cloud Storage, making it the recommended storage for large objects like files and binary data.
Data pipelines. Orvanta enables building fast, powerful, reliable, and easy-to-build data pipelines.
Roles and permissions. Control access and manage permissions within your instance and workspaces.
Authentification. Orvanta provides flexible authentication options to ensure secure access to the platform.
User tokens. Generate API tokens with granular scopes to control access to specific connections and actions.
Error handling. There are 5 ways to do error handling in Orvanta.
Jobs. A job represents a past, present or future task or work to be executed by a worker.
Streaming. Stream job results via SSE, webhooks and HTTP routes.
Jobs runs. Get an aggregated view of past and future runs on your workspace.
Connections and connection types. Connections are structured configurations that link to third-party systems, with Connection types defining the schema for each Connection.
Variables and secrets. Variables and secrets are encrypted, dynamic values used for reusing information and securely passing sensitive data within scripts.
Assets. Visualize your data flow and automatically track where your assets are used.
Environment variables. Environment variables are used to configure the behavior of scripts and services, allowing for dynamic and flexible execution across different environments.
Groups and folders. Groups and folders enable efficient permission management by grouping users with similar access levels.
Workers and worker pools. Worker Pools allow users to run scripts and flows on different machines with varying specifications.
Workspace secret encryption. When updating the encryption key of a workspace, all secrets will be re-encrypted with the new key and the previous key will be replaced by the new one.
Caching. Caching is used to cache the results of a script, flow, or flow step for a specified number of seconds.
Handling files and binary data. In Orvanta, JSON is the primary data format used for representing information. When working with binary data, such as files, they are represented as Base64 encoded strings.
Service logs. View logs from any worker or servers directly within the service logs section of the search modal.
Preprocessors. Preprocessors are used to transform incoming requests before they are passed to the runnable.
Search bar. Navigate through workspace pages & content.
Collaboration in Orvanta. Collaboration in Orvanta is simplified through various features and workflows.
Orvanta AI. Have AI complete code on Orvanta.
AI Agents. Integrate AI agent steps directly into your Orvanta flows.

Hosting & advanced

Infrastructure as code. Manage Orvanta instance configuration declaratively with YAML files or a Kubernetes operator.
Self-host. Run Orvanta on your own infrastructure.
Orvanta on AWS ECS or EKS. Orvanta can be deployed on an ECS or EKS cluster.
Orvanta on Azure. Deploy Orvanta on Azure AKS with optional Entra ID database auth.
Command-line interface. Interact with Orvanta instances right from your terminal.
Local development. Develop from various environments such as your terminal, VS Code, and JetBrains IDEs.
Version control in Orvanta. Sync your workspace to a git repository.
Workspace forks. Create independent copies of workspaces for parallel development workflows, similar to git branches and GitHub forks.
Deploy to prod. Deploy to prod using a staging workspace.
Preinstall binaries. Workers in Orvanta can preinstall binaries. This allows them to execute these binaries in subprocesses or directly within bash.
Browser automation. Run browser automation scripts.
Setup OAuth and SSO. Orvanta supports Single Sign-On for Microsoft, Google, GitHub, GitLab, Okta, and domain restriction.
Sharing common logic. It is common to want to share common logic between your scripts. This can be done easily using relative imports in both Python and TypeScript.
TypeScript client. The TypeScript client for Orvanta allows you to interact with the Orvanta platform using TypeScript in the Bun runtime.
Python client. The Python client library for Orvanta provides a convenient way to interact with the Orvanta platform’s API from within your script jobs.
Set/Get progress from code. You can now set progress of script execution from within the script (Python and TypeScript).
Share on the Orvanta Hub. Share your scripts, flows and connection types on the Orvanta Hub.

Code editor-specific features

Parameter inference. Orvanta ensures that the parameters passed to scripts, flows, and connections match the expected format and type.
Add connections and variables to code. You can directly access Variables and Connections from the Code editor.
Code assistants. Orvanta integrates code assistants into its code editor to provide language-specific suggestions, linting, formatting, and more.

Script-specific features

All details on Scripts can be found in the Script section.

Script kind. You can attach additional functionalities to Scripts by specializing them into specific Script kinds.
Generated UI. Main function’s arguments can be given advanced settings that will affect the inputs’ auto-generated UI and JSON Schema.
Versioning. Scripts, when deployed, can have a parent script identified by its hash.
Concurrency limit. The Concurrency limit feature allows you to define concurrency limits for scripts and inline scripts within flows.
Running services with perpetual scripts. Perpetual scripts restart upon ending unless canceled.
Multiplayer. The Multiplayer feature allows you to collaborate with team members on scripts simultaneously.
Run scripts in VS Code. The Orvanta VS Code extension allows you to run your scripts and preview the output within VS Code.

Flow-specific features

All details on Flows can be found in the Flows section.

Triggering flows. Trigger scripts and flows on-demand, by schedule or on external events.
Testing flows. Iterate quickly and get control on your flow testing.
AI-generated flows. Generate flows from prompts.
Branches. Split the execution of the flow based on a condition.
For loops. Iterate a series of tasks.
While loops. While loops execute a sequence of code indefinitely until the user cancels or a step set to Early stop stops.
Error handler. Configure a script to handle errors.
Trigger scripts. Trigger scripts are designed to pull data from an external source and return all of the new items since the last run, without resorting to external webhooks.
Retries. Re-try a step in case of error.
Concurrency limits. The Concurrency limit feature allows you to define concurrency limits for scripts and inline scripts within flows.
Custom timeout for step. If the execution takes longer than the time limit, the execution of the step will be interrupted.
Priority for steps. Prioritize a flow step in the execution queue.
Lifetime / Delete after use. The logs, arguments and results of this flow step will be completely deleted from Orvanta once the flow is complete.
Cache for steps. Re-use a step’s previous results.
Early stop / Break. Stop early a flow based on a step’s result.
Early return. Define a node at which the flow will return at for sync endpoints. The rest of the flow will continue asynchronously.
Suspend & Approval / Prompts. Suspend a flow until specific event(s) are received, such as approvals or cancellations.
Sleep / Delays in flows. Executions within a flow can be suspended for a given time.
Step mocking / Pin result. When a step is mocked, it will immediately return the mocked value without performing any computation.

Enterprise & cloud features

Enterprise onboarding. Essential setup information and best practices for new enterprise self-hosted customers.
Support & SLA. Our SLAs are designed to provide timely assistance and address any issues.
Audit logs. Orvanta provides audit logs for every operation and action that has side-effects.
Worker pools management UI. Manage Worker Pools through the Orvanta UI.
Autoscaling. Autoscaling automatically adjusts the number of workers based on your workload demands.
Deploy to prod using the UI. Deploy items to another staging/prod workspace.
Git sync. Connect an Orvanta workspace to a Git repository, and use the Orvanta CLI to push and pull scripts and flows between the workspace and the repository.
Workspace protection rulesets. Enforce governance policies on workspace changes to make more robust deployment workflows.
Concurrency limits. The Concurrency limits feature allows you to define concurrency limits for scripts, flows and inline scripts within flows.
Job debouncing. Job debouncing prevents redundant job executions by canceling pending jobs with identical characteristics.
Instance object storage distributed cache for Python, Rust, Go. Leverage a global S3 cache to speed up Python dependency handling by storing and reusing pre-installed packages.
OpenID Connect (OIDC). Use Orvanta’s OIDC provider to authenticate from scripts to cloud providers and other APIs.
SAML & SCIM. Configure Okta or Microsoft for both SAML and SCIM.
External auth with JWT. Generate your own JWT tokens with the desired permissions for your already authenticated users and pass them to Orvanta.
Dedicated workers / High throughput. Dedicated Workers are workers that are dedicated to a particular script.
Agent workers. Agent workers are a 4th mode of execution of the Orvanta binary, but instead of using MODE=worker, we use here MODE=agent.
Critical alerts. Get a notification everytime a job is re-run after a crash.
Content search. Search across scripts, flows and connections for a specific string. On Enterprise Edition this searches your full catalogue; without it, search is capped to a small sample so you can try it before upgrading.
Codebases & bundles. Deploy a TypeScript script together with its local relative imports as a single pre-built bundle, so the imports travel with the deployed version instead of being resolved again at runtime. Bun only, and pushed from the CLI rather than the editor.
Multiplayer. Collaborate on the same script in real time with teammates — cursors and edits sync live, backed by a CRDT (Yjs) over WebSocket.
Private Hub. Point your Orvanta instance at your own Hub deployment to control which scripts, flows and connection types are approved and shared across your instances, instead of the public Orvanta Hub.
White labeling Orvanta. An Enterprise license can carry a whitelabel name; when set, Orvanta’s own name and logo are replaced with yours across the logged-in UI.
Windows workers. Workers can run natively on Windows — no Docker or WSL required — for the Python and Bun executors.
Full text search. The Enterprise tier can index jobs and service logs for full text search, for quick access and better observability out of the box.
SQL to S3 streaming. Stream an SQL query large result to a workspace storage file.