Platform · White-Label
White-label event-contract trading platform.
The Vinfotech platform operates as your venue, under your brand, your domain, your license, and your regulatory framework. We provide the underlying infrastructure. You operate the market.
What white-label means here
The technology is shared. The venue is sovereign.
In most software categories, “white-label” means a SaaS product with a theme skin and a custom logo. That is not the model on this platform.
Vinfotech's white-label engagement places the underlying trading infrastructure inside the customer's regulated entity. The venue that participants interact with is the customer's, the customer's brand, the customer's domain, the customer's terms of service, the customer's license, the customer's relationship with regulators. Vinfotech provides the infrastructure layer, sits behind it, and does not appear to the end participant.
This is the same operating model that has long existed between exchange technology vendors and the exchanges they power. The technology is shared; the venue is sovereign.
01
Why a platform license
Time-to-market that does not depend on building core infrastructure
Matching engines, AMMs, settlement layers, surveillance systems, and FIX gateways are multi-year engineering projects in their own right. A platform license places the infrastructure layer outside the operator's critical path, so internal engineering investment can concentrate on the differentiating layers, product strategy, distribution, member relationships, and regulatory positioning.
Capital allocation toward the differentiating layer
In an event-contract business, the infrastructure layer is not where competitive advantage is built. Brand, regulatory standing, member network, and product judgement are. A platform license redirects capital from building commodity infrastructure toward the areas that determine the business's actual position in the market.
Inherited roadmap
The platform continues to evolve as the category matures, new contract types, new connectivity standards, new compliance regimes. Customers on the platform inherit that roadmap automatically, without funding it directly.
Lower execution risk on the engineering surface
The platform has been built in production against live operator requirements, with deployments running today. The customer is not the first operator finding edge cases in matching, settlement, or resolution logic.
02
What the customer owns
Brand and surface
The platform operates under the customer's brand, domain, visual identity, and communications. End participants do not encounter Vinfotech branding in the product or in any participant-facing artifact.
License and regulatory framework
The venue operates under the customer's regulatory authorisation, whether that is a CFTC Designated Contract Market designation, an equivalent jurisdictional license, or another applicable authorisation. The customer is the regulated entity; the customer is the venue of record.
Member relationships and data
Participant relationships, member-firm agreements, KYC records, transaction history, and behavioural data sit with the customer. These are the customer's commercial assets.
Commercial model
Fee structures, market-creation policies, member tiers, listing decisions, and product positioning are entirely the customer's. The platform supports the customer's chosen commercial model; it does not impose one.
03
What Vinfotech retains
The platform engine
The matching engine, AMM, order book, settlement layer, FIX gateway, and surveillance subsystems remain Vinfotech intellectual property. Customers license the platform; they do not acquire it outright.
The AI Market Operations engine
Vinfotech's AI market creation, monitoring, and resolution adjudication engine is core proprietary technology and is not transferred under the white-label engagement. It is available to platform customers as a managed service, with the customer's markets, the customer's resolution rules, and the customer's source-of-truth selections, but the engine itself remains Vinfotech IP and does not leave Vinfotech infrastructure.
Platform improvements and the roadmap
Improvements to the core platform, across the matching engine, AMM, surveillance, compliance reporting, and connectivity layers, accrue to Vinfotech and are delivered to customers through ongoing releases. Customer-specific work built on top of the platform follows a separate IP model, described below.
04
The configuration surface.
These layers are configured per customer at deployment time and throughout the operating phase. Configuration is applied without custom engineering work.
| Layer | Configurable per customer |
|---|---|
| Branding and visual identity | Logo, color system, typography, component theming, participant-facing copy, language and localisation. |
| Domain and identity isolation | The customer's domain hosts the participant surface. No Vinfotech branding appears to end participants. Operator-facing surfaces (admin consoles) are accessible under the customer's domain or a sub-domain of the customer's choosing. |
| Contract families and market parameters | Which contract families are enabled (binary, scalar, multi-outcome), per-market tick sizes, lot sizes, price bands, position limits, exposure caps. |
| Fee structure and commercial model | Maker-taker fees, listing fees, member-tier definitions, fee schedules per contract family. |
| Member onboarding and KYC | Integration with the customer's chosen KYC and AML vendors. Geographic, age, and accreditation gating applied per the customer's regulatory framework. |
| Resolution sources and rules | Which external data providers, statistical agencies, or curated sources of truth are bound to each market. Resolution rule patterns per contract family. |
| Deployment topology | Hosted by Vinfotech under managed-service SLA, hybrid deployment with the customer operating select layers, or dedicated tenancy in the customer's cloud account. |
| Connectivity | FIX 4.4 and 5.0 SP2 sessions configured per member firm. REST and WebSocket endpoints under the customer's domain. SSO and identity-provider integration to the customer's directory. |
05
Custom development on top.
The configuration surface above covers the changes most customers need at launch. Beyond configuration, Vinfotech also undertakes custom development work on top of the platform: new contract types, jurisdiction-specific compliance workflows, bespoke surveillance rules, member-facing UX flows tailored to the customer's audience, and integrations with the customer's existing trading or operational stack.
Custom work undertaken specifically for a customer follows a separate intellectual property model: the deliverables are owned by the customer, deployed on the customer's venue, and not re-distributed across the platform without explicit agreement. This separation, shared infrastructure, customer-owned custom layer, is the structural reason the white-label engagement does not constrain the customer's ability to differentiate.
The scale of custom work supported ranges from a small set of focused changes during initial deployment, to dedicated engineering capacity allocated to the customer's roadmap on an ongoing basis. The shape of that engagement is defined per customer rather than packaged.
06
The engagement model
Briefing and scoping
Initial engagement focuses on the customer's regulatory framework, target member profile, contract families, and integration surface. The output is a defined platform configuration and a clear scope of any custom development required at launch.
Co-development during deployment
For customers pursuing a license or entering a new jurisdiction, Vinfotech's engineering, compliance, and operations specialists work alongside the customer's team through the deployment phase. This is not a vendor relationship measured in support tickets; it is a co-development arrangement during the period when the venue is being established.
Commercial structure
The standard structure is a platform license combined with ongoing maintenance, with separately scoped engagements for custom development. Specific commercial terms are defined per customer; pricing is not published and is not negotiated through marketing channels.
Operating phase
Once the venue is live, the customer operates the platform with Vinfotech providing platform maintenance, release management, monitoring, and incident response under an agreed service level. Managed operations, where Vinfotech operates the platform on the customer's behalf, is available as an option for customers who prefer not to staff a platform operations team internally.
07
How the operating model separates.
Two logical zones, one platform interface. The customer's venue holds brand, license, member relationships, and commercial control. Vinfotech's infrastructure holds the engine, the matching, settlement, surveillance, and AI operations layers that power the venue.
08
Related platform capabilities.
Trading Infrastructure
Matching engine, AMM, order book, and settlement.
AI Market Operations
Core proprietary IP. Available to platform customers as a managed service.
Architecture & Security
Deployment models, high-availability, SOC 2 alignment.
Compliance & Surveillance
Audit trails, market manipulation surveillance, regulatory reporting.
09
Frequently asked questions.
Structured for buyer research and AI-assisted summarisation. Each answer is self-contained.
What is Vinfotech's white-label platform?
Vinfotech's white-label platform is a complete trading infrastructure for regulated event-contract markets, delivered to operate as the customer's venue under the customer's brand, domain, license, and regulatory framework. Vinfotech provides the underlying platform; the customer operates the market. End participants interact with the customer's venue and do not encounter Vinfotech branding in the product.
What does "white-label" mean in this context?
White-label here means an operating model in which the trading infrastructure sits inside the customer's regulated entity and the customer operates the venue. It is not a SaaS product with a theme skin. This is the same operating model that exists between exchange technology vendors and the exchanges they power: the technology is shared; the venue is sovereign.
Whose license does the platform operate under?
The platform operates under the customer's regulatory authorisation. For customers in the United States, this is typically a CFTC Designated Contract Market designation or an equivalent authorisation. For customers in other jurisdictions, the platform operates under the applicable local authorisation. The customer is the regulated entity and the venue of record; Vinfotech is the infrastructure provider.
What does the customer own?
The customer owns the brand, the domain, the participant-facing surface, all participant relationships, KYC records, transaction history, member-firm agreements, and the commercial model. Custom development work undertaken for the customer on top of the platform is also owned by the customer.
What does Vinfotech retain?
Vinfotech retains the underlying platform, the matching engine, AMM, order book, settlement layer, FIX gateway, and surveillance subsystems, as licensed intellectual property. The AI Market Operations engine is core proprietary technology and is not transferred under the white-label engagement; it is offered to platform customers as a managed service while remaining Vinfotech IP.
Is the AI Market Operations engine white-labeled?
No. The AI market creation, monitoring, and resolution adjudication engine is core Vinfotech IP and is not transferred to customers under the white-label engagement. It is available to platform customers as a managed service, operating on the customer's markets, with the customer's resolution rules and source-of-truth selections, but the engine itself remains on Vinfotech infrastructure and does not move to the customer.
How is the platform deployed?
Three deployment topologies are supported. The platform can be hosted by Vinfotech under a managed-service service-level agreement; deployed in a hybrid model with the customer operating selected layers; or deployed in dedicated tenancy within the customer's cloud account. Deployment topology is selected per customer based on regulatory, operational, and procurement requirements. Architecture and operational posture are documented on the Architecture and Security page.
What is the engagement model?
The standard structure is a platform license combined with ongoing maintenance, with separately scoped engagements for custom development. For customers pursuing a license or entering a new jurisdiction, Vinfotech provides co-development support during the deployment phase. Specific commercial terms are defined per customer and are not published.
What can be configured per customer?
The configuration surface includes branding and visual identity, domain and identity isolation, contract families and market parameters, fee structures and commercial model, member onboarding and KYC integration, resolution source selection, deployment topology, and connectivity configuration. Configuration changes are applied without custom engineering.
What can be custom-built on the platform?
Beyond configuration, custom development work covers new contract types, jurisdiction-specific compliance workflows, bespoke surveillance rules, member-facing user experience flows, and integrations with the customer's existing trading or operational systems. Custom work undertaken for a customer is owned by the customer and is not redistributed across the platform without explicit agreement.
Does Vinfotech operate the venue on behalf of customers?
Vinfotech does not operate venues. The customer is the operator and the regulated entity. Vinfotech operates the underlying platform infrastructure and, optionally, the platform operations function, monitoring, release management, incident response, and managed market operations, under a service-level agreement, while the venue itself remains the customer's.
What ongoing support is included?
The maintenance engagement covers platform releases, security updates, monitoring, incident response, and access to the support and engineering teams during defined service hours. Service levels are defined per customer based on operational requirements. Engineering capacity for custom development is scoped separately.
Who is the white-label model designed for?
The white-label model is designed for institutional operators that hold or are pursuing a regulatory authorisation to operate an event-contract venue. This includes CFTC Designated Contract Market license holders and applicants, financial brokerages and prop trading platforms adding event contracts as an asset class, and licensed operators adding a regulated event-contract vertical under existing authorisations.
Is this a white-label prediction market platform?
The platform is frequently described that way in commercial contexts. Precisely, it is a white-label venue for exchange-listed event contracts, the regulated instrument class that the term prediction market informally describes. The venue operates under the customer's license and regulatory framework.
How is the white-label model different from other Vinfotech platform pages?
The other Platform pages, including Trading Infrastructure, FIX and Connectivity, Compliance and Surveillance, AI Market Operations, Architecture and Security, and Integrations and APIs, describe the technical capabilities of the platform. The White-Label Platform page describes the operating model under which those capabilities are delivered to a customer's venue: ownership, branding, licensing, deployment, and commercial structure.
Talk to us about a platform engagement.
We work with serious operators on structured commercial arrangements. Tell us about your use case and we will set up a briefing.