Features and Pricing

Powerful tools for systems engineering teams of every size

Delta Map

Compare model baselines and track every change.

Connects to your modeling tool, captures snapshots at any point in time, and generates detailed comparison reports highlighting exactly what changed.

Automated model capture from MBSE models
Side-by-side diff with element-level change tracking
Configurable comparison rules and filters
Exportable delta reports for review boards
SVG diagram capture and visual comparison

Viz

Interactive dashboards built for engineering data.

Create visualizations from model data, requirements, and project metrics using chart types optimized for systems engineering workflows.

D3.js, Chart.js, and custom visualization types
Interactive dashboards with drill-down capability
Import data from spreadsheets, APIs, or directly from your model
Shareable views and embeddable charts
Sunburst, scatter, bar, treemap, and more

Review

Structured design reviews with full audit trails.

Organize review packages, assign reviewers, track approval status, and maintain a complete record of every decision made during the review process.

Structured review packages with approval workflows
Per-element approve / reject with inline comments
Reviewer access tokens for external stakeholders
Technical Review Board (TRB) package management
Progress dashboards and review metrics

Workspace

Unified project hub — includes Delta Map, Viz, and Review.

The connective tissue between analyses, dashboards, and reviews — giving your organization a single source of truth for every engineering effort.

Includes full access to Delta Map, Viz, and Review
Dedicated workspaces per project with linked artifacts
Threaded discussions and timeline of events
Saved views of critical data across tools
Cross-tool traceability and decision tracking

Pricing

Per user, per month — billed annually. Graduated volume discounts applied automatically.

Online (SaaS)

Hosted and managed by Veyla. Per-user rate by bracket — each additional user is billed at the rate for their bracket.

Core Pro Popular Complete

Users	Delta Map	Viz	Review	Workspace Includes Delta Map, Viz & Review
76+	Contact us for volume pricing Get Started with up to 75 users, or contact us for larger teams.

Graduated pricing: your first user is billed at the Individual rate, users 2–5 at that tier's discounted rate, and so on.

Core Pro Complete

1 user

Feature	Full Price	Your Price	Discount

Prices are per user per month, billed yearly.

Estimate Yearly Cost

Select the features you need to see your estimated annual cost.

Delta Map

Viz

Review

Workspace All 3 features bundled

Feature	Monthly	Yearly

Included Usage

All plans include usage quotas. Complete customers can add overage capacity for uninterrupted workflows. AI operations are session-based - daily limits are per user.
If you run into a limit, contact us and we'll work with you to increase your quota - we're still optimizing and want our limits to be generous.

Help me choose	Core	Pro Most Popular	Complete
AI-Assisted Operations	50 / day	500 / day	7,500 / day + overages
Model API Operations	500 / day	2,000 / day	Unlimited
Storage	500 MB + 250 MB/user	2 GB + 500 MB/user	5 GB + 750 MB/user + overages
Projects per user	25	300	Unlimited^*
Captures per user	100	2000	Unlimited^*
Visualizations per user	200	3000	Unlimited^*
View-Only Accounts	N/A	1 per 10 users	1 per 5 users (with comment permission)

^* Within storage limits.
Complete-tier overage pricing for storage is usage-based and billed monthly. Set your own overage budget to control costs. All quotas are configurable — contact us if your team needs a custom allocation.
View-only accounts are included at the ratios above and can be purchased separately for any tier. Viewers can view and interact with visualizations, view model reviews (and comment at Complete level), and view deltamap reports. Viewers cannot access captures, tree view, or analysis features.

Self-Hosted

Deploy on your own infrastructure. Same pricing as online with a minimum of 25 users.

Get Started

The containerized build undergoes multi-layer security hardening during the build process, reducing known vulnerabilities by over 90% overall compared to an unhardened base image. Every build is automatically scanned and the results are included in the deployment package.

Hardening Approach

The production container is built using a multi-stage Docker pipeline that separates build-time tooling from the runtime image. This means compilers, package managers, and development libraries used during compilation are never present in the deployed container.

Runtime image hardening includes:

Development toolchain removal — Build compilers, header files, and development libraries are stripped from the final image. These packages are the single largest source of reported CVEs in containerized applications and serve no purpose at runtime. This alone eliminated over 500 HIGH-severity findings.
Unused image processing libraries removed — The image processing subsystem ships with optional format loaders (scientific imaging, print rendering, legacy raster formats) that are unnecessary for Deltamap's document and visualization workflows. Removing these eliminated all remaining CRITICAL-severity findings attributable to third-party libraries.
Security patch application — Each build applies the latest available OS-level security patches, ensuring the container ships with current fixes rather than the base image's original package versions.
Non-root execution — The application runs as an unprivileged user (UID 1000) with no elevated capabilities.
No remote access surfaces — SSH, remote shells, and debugging tools are not installed. Container access is limited to docker exec by operators with Docker permissions.

Vulnerability Reduction Summary

Severity	Unhardened	Hardened	Reduction
Critical	25	4	84%
High	573	21	96%
Medium + Low	2,271	250	89%
Total	2,869	275	90%

The remaining findings are predominantly in upstream OS base packages where patches are not yet available from the distribution. These are monitored and addressed in subsequent builds as fixes are released.

Minimal Threat Surface

Even before hardening, the container's external threat surface is inherently narrow: single network port, no inbound services — no SSH, no management ports, no health-check endpoints exposed externally, secrets externalized, read-only capable.

The hardening effort ensures that even the internal contents of the container — which are not directly reachable from outside — meet a high security standard. This matters for defense-in-depth: if an attacker were to gain code execution inside the container, the reduced package surface limits the tools available for lateral movement or privilege escalation.

Security Reports

Each build produces two artifacts included in the provided deployment package.

Self-hosted deployments run entirely on your infrastructure with no internet dependency. Here's the end-to-end process from purchase to users working in the platform.

Purchase & Provisioning

Vendor + Customer

Customer selects a self-hosted plan and completes purchase
Vendor provisions a deployment package containing:
- Containerized application image (Docker)
- License server installer (Java JAR + startup scripts)
- Security scan reports for the container image

License Server Setup

Customer IT

Install the license server on a physical or virtual machine (not inside Docker)
Run the installer script — creates a background service on port 8087 (configurable)
The license server must be network-accessible from the machine that will run the Docker container (can be the same machine)
Run --machine-info to generate a plain-text machine fingerprint — safe for security review before transmitting to the vendor

License Activation

Customer IT

Vendor generates a cryptographically signed .lic file bound to the machine fingerprint
Place the file in the license server's licenses/ directory or upload through the application
The license server validates the signature and activates the license automatically
Additional licenses can be uploaded later as new features or seats are purchased

Application Deployment

Customer IT

Load the container image and start with docker compose up
The container connects to the license server on the host machine
No internet access required — all license validation is performed locally

Admin Setup & User Management

Administrator

First login with the default admin account triggers a setup wizard: change email, set a new password, accept Terms of Service
Admin creates individual user accounts — each user receives credentials and must change their password on first login
Admin assigns licensed features to users individually (named-user licensing: one license per person, no account sharing)

User Access

End Users

Users log in from any machine with network access to the Docker host
On first login: accept Terms of Service and change password
Users only see and access the features assigned to them by the administrator
No direct access to the license server is needed — only the application container communicates with it

Network Architecture

Users

Browser

Docker Host

Application Container

Port 3000 (default)

License Server

Host Machine

Port 8087 (default)

Users need network access to the Docker host. Only the Docker host needs access to the license server. The license server and Docker container can run on the same machine.

All ports are configurable — adjust via environment variables in the provided docker-compose.yml and license server configuration. No rebuild or redelivery required.

All plans include onboarding support and access to our engineering team.

Get Started Back to Home