What is Vince Platform?

Vince Platform is an integration and automation platform for operations and supply chain teams. At its core it does one thing well: it connects business systems, moves data between them, and reshapes that data along the way — reliably and at scale. Everything else in the product is built on top of that core.

As of October 2026, more than 245 companies in 21 countries use Vince Platform, running more than 4.5 million workflows every month.

• Connect — authenticate against ERPs, cloud services, databases and file endpoints through managed connections, so credentials live in one place and are reused across integrations.
• Build — compose workflows from ready-made components, store state in tables, and put results in front of people through apps, dashboards and Excel.
• Run — execute on a serverless architecture that scales with load, with every run visible in Execution Logs.

The core: workflows

Workflows are the essence of the platform. Every workflow has the same three-part shape — Trigger → Transform → Publish — read left to right:

	What it does	Examples
1. Trigger	Something starts the workflow	A schedule · a change in a table · an incoming API call · a user in VXL Live · a dashboard widget · a file landing on SFTP
2. Transform	The data is shaped, filtered, enriched and validated	Transform steps using JSONata, plus lookups against connected systems
3. Publish	The result goes wherever it needs to go	API calls · tables · email · external SFTP · VXL Live · dashboards

The transform layer is where most of the integration logic lives, and it is built on JSONata — a no-code transformation language inspired by XPath and XSLT. It looks unfamiliar for the first hour; after that, complex mappings become short and readable. See the JSONata Masterclass.

Workflow Architecture 101 is the authoritative explanation of this model, and of the handful of workflow shapes that cover most real integrations.

Built on the core

The same platform and the same toolbox power a growing set of products. Each one gives you more value from the platform you already run, and each one is built with the components described in these docs.

Product	What it adds
Workflows	The integration engine itself — triggers, transforms, connections, execution logs
Tables	A queryable data layer inside the platform, for state, snapshots and audit trails
App Builder	AI-generated business apps on top of your workflows and tables, published to users without frontend code
VXL Live	Run workflows from inside Microsoft Excel
Peppol	Send and receive electronic documents over the Peppol network, as workflow steps
AI assistant (Ask Frøy)	In-product help that understands the platform and your context

Vince has a dedicated innovation team whose job is to keep expanding the platform, with a particular focus on AI. New capabilities arrive as additions to the same core, not as separate products to learn.

System agnostic

The platform does not favour one endpoint over another. Infor M3 is one of the systems it connects — a very well-supported one, see Vince Platform and Infor M3 — but a workflow calls a CRM, a webshop or a BI tool with the same components it uses for the ERP.

Examples of systems customers integrate towards: Infor M3, Infor LN, Infor WMS, Shopify, Magento, Crystallize, Salesforce, HubSpot, HiiRetail, Power BI and Fotoware — in practice anything with an API, a file interface or an event stream.

Built for customers to own

Vince Platform is designed so that the people who know the business can build, change and run their own integrations. A typical pattern is that Vince builds the first integrations together with the customer, and the customer's own team takes over from there — adding flows, adjusting mappings and reading execution logs themselves. Vince's team is there when extra hands are needed, not as a prerequisite for every change.

That is also why these docs exist: the component reference, how-to guides and integration patterns are written for the people who will own the integrations after go-live.

Governance: an alternative to shadow IT

When the official tools are too slow to change, business teams build their own: spreadsheets with macros, small databases, personal automation flows, and now apps generated with AI tools — often with copied passwords and data extracts on someone's laptop. This is called shadow IT. It solves the problem of the day, but nobody in IT knows it exists, who uses it, or what data it touches, and it breaks when its builder leaves.

Vince Platform gives business teams the same speed inside one platform that IT controls:

• Credentials stay in one place. Workflows, apps and Excel tools reach your systems through shared Connections. Nobody needs their own copy of an ERP password, and an app never connects to a system directly.
• Access is role-based. Administrators decide who can build, publish and run each kind of thing; see App Builder permission levels. External partners get their own users and only the access you give them.
• Everything is visible. Every workflow run is in the Execution Logs, and the Audit Log records who changed what and when.
• Business rules live in shared workflows, not inside each app or spreadsheet. Change a rule in the workflow and every app and Excel tool that calls it uses the new rule, as long as the workflow's inputs and outputs keep the same shape.
• Publishing is controlled. An app reaches its users only when someone with Deploy access publishes a version, and the Tenant Prompt applies your company's standards to every app built.
• Business data stays out of the AI. During an app build the AI sees field names and structure, not your data; see What the AI sees during a build session.

The result: the people who know the business still build their own tools, and IT can see, secure and support every one of them. For the security details an IT or security review needs, see the Security Overview.

Is Vince Platform a good fit?

Vince Platform is a good fit when:

• Your work depends on data moving between business systems — an ERP such as Infor M3, a webshop, a CRM, a warehouse system, files from partners — and you want those integrations built, changed and monitored in one place.
• You want business apps, dashboards or Excel tools on top of that data without writing frontend code. App Builder generates the app; your workflows and tables supply the data and the business rules.
• Business teams are building their own tools anyway, and IT wants those tools in a governed platform instead of spreadsheets and personal accounts — see Governance.
• The users are your own staff or business partners you know, such as suppliers, transporters and customers. Partners sign in with their own Vince Platform user, and roles control what each of them sees — see external users and portal access.

It is not designed for:

• Public apps where anyone can sign up on their own. Every app user is a Vince Platform user that your administrator gives access to.
• Building a standalone software product with its own code base and hosting. Apps built with App Builder run inside Vince Platform, on top of its workflows and tables. Their code can be exported, but its data calls go to Vince Platform APIs and must be replaced to run anywhere else.
• On-premises installation. Vince Platform is only available as a service hosted by Vince.

Where to go next

• New to the platform? Start with Workflow Architecture 101, then build your first workflow with the component reference.
• Running Infor M3? Read Vince Platform and Infor M3.
• Looking for ideas? Browse the Integration Patterns and the Concept Catalog.