VIKTOR
VIKTOR is a browser-based Python application platform for engineers that ships AI-assisted app authoring, integrations with CAD and analysis tools, and governed sharing across free community tiers and paid company plans.
VIKTOR hosts engineering micro-applications in the cloud so specialists can wrap scripts, Grasshopper or Dynamo logic, and spreadsheets in guided web experiences instead of handing static files between teams. Product pages describe more than two hundred UI and automation primitives (inputs, 3D views, maps, charts, and report exporters) meant to shorten the distance from a working Python routine to a form other disciplines can run safely (VIKTOR, 2026).
Integration messaging focuses on cutting manual hand-offs: connectors and worker patterns talk to common FEM, CAD, and common data environment tools from major vendors, while databases and geospatial feeds can supply live parameters to calculations. A documented REST API supports server-side calls from languages beyond Python, and apps can chain together so outputs from one workflow feed the next without rebuilding glue code for every project.
Commercial packaging spans a long-term free tier for public apps, paid tiers that unlock private apps, Git-based development, integrations, and support hours, plus enterprise options with SSO, multi-region hosting, and expanded seat counts. VIKTOR states the free tier stays available without a time limit for community experimentation, while production or client-facing use generally moves onto a paid plan with the right security and support profile.
Because the same platform hosts lightweight calculators beside heavier BIM or IFC utilities, governance features matter: role definitions, audit expectations on upper plans, optional branded workspaces, and viewer seats for people who only execute published apps. Buyers should map their required identity provider, data residency, and support SLAs directly with VIKTOR before relying on the stack for regulated work.
Specifications
Pricing
Platforms
Used for
Used by
Tasks
Pros and cons
Pros
- Keeps logic in Python while exposing it through governed web apps non-developers can run.
- Combines no-code app assembly with full code paths for teams that outgrow visual tools alone.
- Published plans clarify free community use versus paid private and enterprise features.
- Documentation and REST APIs support automation outside the browser when needed.
Cons
- Seat mixes across Core, Basic, Viewer, and external users need upfront planning to avoid surprise limits.
- Deep desktop integrations still depend on stable worker machines or vendor connectors you must maintain.
- Exact pricing for paid tiers is quote-based, so budget owners need a sales or trial conversation.
Key features
Python-first apps: Wrap engineering scripts and libraries in hosted web apps with inputs, validation, and results pages.
Large control library: Marketing materials cite more than two hundred building blocks spanning forms, 3D views, maps, plotting, and document export.
CAD and solver ties: Connectors and workers integrate desktop CAE and CAD packages so browser users can trigger governed calculations remotely.
AI app builder: Built-in assistants help author or extend applications without typing every boilerplate line by hand.
Enterprise controls: Paid tiers add SSO options, audit tooling on qualifying plans, regional hosting choices, and structured support bundles.
Public gallery: Sample IFC, structural, MEP, and architecture demos ship as templates you can study or fork.
Pricing
Free
per month
Free
Includes one free user seat, public apps, App Builder AI, and community support per VIKTOR; verify current limits on viktor.ai/plans.
Individual
Free
Adds private apps, integrations, Git workflows, and email support; pricing is contact-based on the public plans page.
Enterprise
Free
From twenty Core seats and one hundred Basic seats in marketing copy, with SSO, multi-region hosting options, and expanded support hours; request a formal quote.
Frequently asked questions
What is VIKTOR used for in AEC and BIM teams?
- Teams use VIKTOR to turn Python engineering scripts, Grasshopper or Dynamo definitions, and spreadsheet logic into browser apps colleagues can run with guided inputs. Typical examples include IFC checks, structural calculators, hydraulics utilities, and reporting flows that replace emailed Excel files.
Is VIKTOR free?
- VIKTOR offers a free tier with a free user seat for building and publishing public applications and using community support. Private apps, integrations, expanded collaboration, and enterprise security features require a paid plan, and VIKTOR states the free tier has no fixed end date for eligible community use.
Does VIKTOR work with Revit, IFC, or other BIM data?
- Documentation and marketing pages describe importing 3D content from sources such as Grasshopper, Dynamo, and Revit, and the public demo list includes IFC-centric sample apps. You still need to confirm file-size limits, worker sizing, and licensing for your specific BIM toolchain inside a pilot project.
Do you need to know Python to use VIKTOR?
- Power users can write Python directly, while the platform also advertises a drag-and-drop App Builder and spreadsheet-to-app utilities for faster starts. Complex integrations and long-term maintenance usually involve Python or supported APIs, so plan for developer time even if the first app is no-code.
How does VIKTOR pricing work for companies?
- Published plans range from the free community tier through Individual, Small business, Business, and Enterprise packages with different Core and Basic seat counts, support hours, and optional SSO or branded environments. List prices are not shown for paid tiers, so teams should contact VIKTOR or use the self-serve signup flow to match seats and compliance needs.
Can VIKTOR integrate with databases and other cloud systems?
- Product pages describe REST API access, database connectivity for engineering data, and hooks into company systems so apps can read parameters and write results under your security rules. Enterprise tiers add audit and hosting options that matter when connecting to production data stores.