Keep the customer relationship
Sell under your own positioning and stay responsible for the audience, acquisition, and first-line communication.
VUST White Label
Launch your own AI service in as little as 14 days.
You bring the audience, customers, and sales. VUST provides the branded product, infrastructure, updates, and technical operations.
For accepted, fixed-scope Partner Launch engagements. The clock starts after the signed scope, setup payment, brand assets, access, legal details, and launch approvals are complete.
One shared VUST product core. One accountable partner. No source-code fork.
01 · Your brand
Audience, positioning, sales, and customer relationship
02 · VUST
Product core, selected tools, infrastructure, and operations
03 · Your customers
A focused paid service under your positioning
Distribution is the advantage
Your audience wants useful AI. They do not need another unfinished demo.
Connecting one model is easy. Operating a customer product means onboarding, reliable delivery, provider routing, usage controls, monitoring, updates, support, and a commercial model that survives real use. A partner who already understands a market can move faster by starting from an operating product core.
Launch a focused package
Start with the customer jobs that matter instead of funding a broad platform before demand is proven.
Build recurring potential
Test a repeatable service and retail model without pretending that revenue, margin, or retention is guaranteed.
Transparent assumptions
Model contribution before you commit.
Change every assumption: paid customers, retail price, platform cost, provider usage, and your own acquisition and support costs. The defaults are an illustration—not VUST pricing, a quote, or a forecast.
Customer revenue$2,900.00
Platform assumption-$600.00
Total provider usage-$400.00
Partner costs-$500.00
Estimated monthly contribution
$1,400.00
Illustrative scenario — not a revenue guarantee.
Editable assumptions — not VUST pricing or a quote.
Contribution is shown before tax, financing, overhead, refunds, chargebacks, and other business costs. It is not profit. A signed commercial proposal replaces every illustrative assumption.
Decision formula
Estimated monthly contribution = paid customers × retail price − VUST platform fee − provider usage − partner acquisition and support costs
A bounded launch package
What ships is classified before work begins.
We agree one package and one acceptance matrix before implementation. Anything outside that scope is planned, priced, or declined explicitly.
- One approved customer-facing brand configuration.
- One agreed domain configuration, subject to DNS access and verification.
- One curated package of already-supported VUST tools.
- One responsive web entry surface.
- One branded Telegram entry point when included in the signed scope.
- Basic onboarding, package/limit presentation, usage accounting, monitoring, launch guidance, and acceptance QA.
- Additional tools, markets, languages, integrations, or Telegram entry points.
- Expanded reporting, migration, design, sales-material, or legal-copy support.
- Approved custom features or dedicated infrastructure scoped separately.
- Self-service partner dashboard.
- Automated tenant, domain, certificate, or secret provisioning.
- Reseller checkout, split settlement, and marketplace billing.
- Automated customer export and deletion portal.
Source code, repository access, a partner-specific fork, unlimited custom work, and revenue guarantees are not included.
Fixed scope, controlled launch
Four stages. One acceptance owner on each side.
Fit and commercial scope
Confirm the audience, customer job, package, support owner, budget, market, legal fit, and success evidence.
Brand, domain, and package configuration
Receive approved brand assets, DNS access, legal details, tool selection, customer contact, and required credentials.
Implementation, content, and QA
Configure the agreed surfaces and validate delivery, usage, monitoring, content, support handoff, and rollback.
Partner acceptance and launch
Sign the acceptance matrix, begin with a controlled cohort, and expand or roll back from evidence.
The 14-day target begins only after every prerequisite is accepted. Missing access, payment, approval, third-party review, or a scope change pauses the schedule.
An operating foundation
Product infrastructure underneath your brand.
- Supported VUST tools already operate across current web and Telegram surfaces.
- Shared provider clients and routing support selected production tools.
- Server-side usage accounting and structured operational monitoring exist for supported paths.
- VUST maintains the shared product core and technical escalation.
Partner Launch is scoped delivery on that foundation, not automated tenant provisioning. Partner-specific identity, billing, data separation, domain, and exit requirements are acceptance gates whenever they are in scope.
Browse current VUST toolsQualify before building
The strongest partner already knows how customers will arrive.
Best fit
- An existing audience, customer base, community, or repeatable acquisition channel.
- A clear vertical and customer job.
- One accountable owner for positioning, sales, and approvals.
- Capacity to handle L1 support and customer communication.
- Setup and operating budget.
Not a fit
- No distribution or acquisition plan.
- A request for source-code ownership or repository access.
- Unlimited bespoke development inside the launch scope.
- A one-off personal bot.
- No commercial or support owner.
Choose the right operating relationship
Start with Partner Launch. Expand only when evidence justifies it.
Partner Launch — primary
One fixed package, agreed brand/domain surfaces, named responsibilities, prerequisites, and acceptance matrix.
Full White Label — planned deeper scope
Broader brand, market, reporting, integration, and operating requirements assessed after the first package.
Enterprise — direct VUST engagement
A company integrates VUST capabilities into its existing product or workflow without operating a separate partner brand.
No public price, SLA, entitlement, or availability is implied for the later levels.
Clear before the contract
Frequently asked questions
What is actually white-labeled?
The signed scope can cover the customer-facing name, approved visual configuration, domain entry surface, package presentation, onboarding, and a branded Telegram entry point. The underlying VUST product core remains shared and operated by VUST.
Who owns the customer relationship?
The partner owns audience development, acquisition, sales, retail positioning, customer communication, and L1 support. VUST owns the agreed product operation and technical escalation.
Can we set our own retail price?
Retail positioning is agreed during scoping, subject to the signed commercial model, payment rail, taxes, refunds, market law, and sustainable usage economics. The page does not grant unrestricted pricing rights.
Who provides support?
Your team handles L1 onboarding and customer communication. VUST handles L2 product support and coordinates L3 provider or infrastructure escalation. No public response-time or uptime SLA applies unless contracted.
What does the 14-day launch include?
It covers an accepted fixed package: agreed brand/domain configuration, selected supported tools and surfaces, content, usage controls, monitoring, support handoff, QA, and controlled launch. Custom platform work is outside that promise.
When does the 14-day timeline start?
After the signed scope, cleared setup payment, approved assets, DNS/access, legal and business details, tool/package decisions, support contacts, credentials, and acceptance owner are complete.
Can we request new tools?
Yes, but they are assessed as an add-on or later phase. A request is not a promise that the tool is available, safe, economical, or inside the original timeline.
Is source code included?
No. Partner Launch does not include source-code ownership, repository access, or a partner-specific code fork.
Can VUST be completely hidden?
Brand disclosure is decided during contracting and legal review. We do not promise that VUST can always be hidden across every product, payment, provider, legal, or support surface.
How is usage charged?
The contract separates fixed setup, recurring platform/operations, provider usage, included support, and excess support. Exact units, rates, allowances, reconciliation, and adjustments are agreed before launch.
Can we use our own domain?
It can be included in the signed scope, subject to approval, DNS access, verification, legal details, technical constraints, and an exit process. Automated custom-domain provisioning is not self-service today.
What happens if we stop the service?
The contract must define notice, final accounting, customer communication, domain/bot/asset handling, data export, retention, deletion, and access revocation. There is no silent or improvised exit.
How is customer data separated?
Separation is an acceptance requirement for any partner data path, but VUST does not claim an automated tenant-aware platform or certified isolation already exists. Each selected identity, history, entitlement, usage, cache, log, and admin boundary must pass review.
Does VUST process or store raw prompts?
The answer depends on the selected tool, history behavior, provider route, support process, and contracted retention. “No storage” is not a blanket VUST claim; the data flow is documented during scoping.
Can the solution later move to dedicated infrastructure?
Dedicated infrastructure may be scoped as a paid follow-up when security, scale, geography, or procurement evidence justifies it. It is not included by default and has no public timeline or price.
Start with the market
Bring the audience. We will bring the product.
Tell us who you serve, the workflow you want to package, and how customers will find it. We will test the fit, define the smallest credible scope, and say clearly what is included, planned, optional, or not supported.
Fixed scope. Qualified partners. No commitment from opening a conversation.