- 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.
- Onboarding, package and limit presentation, usage accounting, monitoring, launch guidance, and acceptance QA.
VUST White Label · Partner Launch
Your audience. Your brand. A working AI product.
VUST Partner Launch turns your distribution into a branded AI service your customers pay for. You keep the brand, the pricing, and the customer relationship. VUST operates the product — tools, infrastructure, updates, and monitoring.
Launch-ready in as little as 14 days once scope, assets, and approvals are complete
Illustrative configuration
desk.brightside.co
Brightside & CoTeam plan · 340 / 500 credits
Your client work, faster. Start with a proposal draft or a research brief.
Rephrase
Summary
Search
Grammar
Brightside & Co@brightside_desk_bot
Welcome to Brightside Desk. Five tools for client work — pick one to start.
RephraseSummarySearch
01 · Ownership
You own the customer. VUST runs the machine.
The partner owns everything the customer sees and pays for. VUST owns everything that has to keep working underneath it.
You own
- Your brand — the name, the look, and the story customers buy into
- The customer relationship — your list, your community, your accounts
- Retail positioning — packaging and price point, agreed in scope
- The acquisition channel — how customers find and join the service
- First-line support — onboarding and everyday customer communication
VUST operates
- Product core and tools — one shared, maintained codebase — no fork
- Web and Telegram surfaces — the delivery your customers actually use
- Provider infrastructure — routing and operations across AI providers
- Usage controls — server-side accounting, limits, and plan logic
- Updates and escalation — monitoring, maintenance, and L2/L3 support
Retail positioning and price point are agreed during scoping, subject to the signed commercial model and market rules.
02 · What you could launch
Three launches you could run this quarter.
A Partner Launch ships one curated package of supported VUST tools under your brand. These three are illustrative configurations — not client case studies.
Brightside & Codesk.brightside.co · @brightside_desk_bot
A private AI desk an agency sells to its own team and select clients: faster proposals, cleaner writing, quicker research — under the agency's name, on the agency's domain.
RephraseSummarySearchGrammarPrompt
Illustrative configuration — not a client case study- Buyer
- Agencies, consultancies, and studios selling client work
- Customer jobs
- Proposal improvement · client research · meeting and document summaries · professional writing · content preparation
- Delivery
- Web app on the agency's domain + branded Telegram entry point
- Possible retail model
- Seat-based monthly subscription for the team and select clients
- VUST operates
- Product core, provider routing, usage accounting, monitoring, updates, technical escalation
Fieldnotemembers.fieldnote.club · @fieldnote_bot
A members-only toolkit a creator ships to a paid community: ideas, scripts, and polish — a concrete product benefit attached to the membership.
PromptRephraseHumanizerTranslateSummary
Illustrative configuration — not a client case study- Buyer
- Creators and paid communities with an engaged audience
- Customer jobs
- Content ideas · scripts · text improvement · image and short-video preparation where supported · community utilities
- Delivery
- Members area on the community's domain + branded Telegram entry point
- Possible retail model
- Membership add-on or a standalone community subscription
- VUST operates
- Product core, provider routing, usage accounting, monitoring, updates, technical escalation
Studylineapp.studyline.io · @studyline_bot
A study companion an education business bundles with its courses: explanation, summaries, and translation on the student's level — sold per student, under the school's brand.
StudyTranslateGrammarSummaryMarkdown
Illustrative configuration — not a client case study- Buyer
- Courses, schools, and education businesses
- Customer jobs
- Explanation · summaries · translation · writing improvement · study utilities
- Delivery
- Student portal on the school's domain + branded Telegram entry point
- Possible retail model
- Per-student monthly plan, bundled with the course
- VUST operates
- Product core, provider routing, usage accounting, monitoring, updates, technical escalation
03 · Product experience
One service. Two surfaces your customers already use.
The customer-facing service runs on your domain on the web and as a branded Telegram entry point — the same tools, the same account, the same limits. Shown here: Brightside & Co, the agency configuration selected above.
desk.brightside.coOwn domain
Brightside & CoSigned in as customerTeam plan · 340 / 500 credits
Your client work, faster. Start with a proposal draft or a research brief.
RephraseTone-shift client copy
SummaryDocs and calls to notes
SearchSourced client research
GrammarPublish-ready writing
PromptReusable brief templates
Usage this month340 / 500 credits
Brightside & Co@brightside_desk_botTelegram
Welcome to Brightside Desk. Five tools for client work — pick one to start.
RephraseSummarySearchGrammarPrompt
Summarize this discovery call transcript.
Done — 6 key decisions, 3 open risks, and the follow-up list. Want it as an email draft?
Team plan340 / 500 credits
Illustrative configuration · Mockup — not a live partner service
04 · The alternatives
Four ways to ship an AI product to your audience.
| Build in-house | Assemble no-code tools | Commission a one-off bot | VUST Partner Launch | |
|---|---|---|---|---|
| Time to credible launch | A product team and months of unglamorous plumbing before the first customer. | Fast to demo — slow to make reliable, billable, and supportable. | Fast to ship once. Every change reopens the project. | A fixed 14-day scope once prerequisites are complete. |
| Maintenance ownership | Yours, forever. | Yours, spread across vendors. | Whoever built it — if they answer. | VUST maintains the shared product core. |
| Provider operations | You negotiate, route, and monitor providers yourself. | Per-tool API keys and separate bills. | One hardcoded provider, one point of failure. | Shared provider routing, operated by VUST. |
| Monitoring & usage controls | Built from scratch. | Partial, vendor by vendor. | Rarely included. | Server-side accounting and monitoring included. |
| Commercial ownership | Yours. | Yours, minus per-seat vendor fees. | Yours. | Yours — brand, pricing, and the customer relationship. |
| Customization boundary | Unlimited — at your cost. | Whatever the tools allow. | Whatever was quoted. | A defined package; extensions scoped explicitly. |
No cost or duration figures are claimed for the alternatives — teams, tools, and vendors vary too much for honest numbers.
05 · Economics
Model the contribution before you commit.
Every figure below is your assumption. VUST has no public White Label pricing — a signed commercial proposal replaces everything on this panel. Load a sample scenario or enter your own numbers.
Nothing is pre-filled on purpose.
There is no public VUST pricing to anchor on. Load a neutral sample scenario or type your own assumptions — the contribution, waterfall, and break-even point appear here.
Illustrative scenarioNot VUST pricingNot a revenue guaranteeContribution is not profit
Contribution is shown before tax, financing, overhead, refunds, chargebacks, and other business costs. The platform + operations figure is your placeholder for a quoted price — it is not a published VUST rate.
06 · What ships
The launch package is defined before work begins.
One package, one acceptance matrix. Anything outside it is planned, priced, or declined explicitly — before implementation, not after.
- 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.
Not included at any tier: source code, repository access, a partner-specific fork, unlimited custom development, or revenue guarantees.
07 · Launch journey
Five stages. As little as 14 days.
Scope
Audience, customer job, package, support owner, budget, market and legal fit — agreed and signed.
Brand & package
Approved brand assets, DNS access, legal details, tool selection, and credentials received.
Build & configure
Agreed web and Telegram surfaces configured; content, limits, and usage accounting set up.
QA & handoff
Delivery, monitoring, support handoff, and rollback validated against the acceptance matrix.
Controlled launch
Start with a controlled cohort. Expand — or roll back — from evidence, not hope.
The 14-day target starts after the signed scope, setup payment, approved brand assets, access, legal details, package decisions, and acceptance owner are complete. Missing prerequisites or scope changes pause the clock.
08 · Built on VUST
Not a template. An operating product platform.
Your launch runs on the same maintained core as VUST's own production tools — live today on web and Telegram.
- 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 — one codebase, no partner forks.
Translate
Grammar
Rephrase
Summary
Search
Prompt
Study
Humanizer
Markdown
CV
10 production tools · Web + Telegram
09 · Best fit
Built for partners who already own distribution.
The strongest launches start with
- An existing audience, customer base, community, or repeatable acquisition channel.
- A clear vertical and a customer job you can name in one sentence.
- One accountable owner for positioning, sales, and approvals.
- Capacity to handle first-line support and customer communication.
- A setup and operating budget.
Better served by something else
- You need source-code ownership or repository access — Partner Launch runs on the shared VUST core.
- You want unlimited bespoke development inside the launch scope.
- You are looking for a one-off personal bot rather than a customer-facing service.
- There is no distribution plan yet — build the audience first; we will still be here.
- No one on your side can own commerce and support.
10 · Engagement levels
Start with Partner Launch. Expand from evidence.
Partner Launch
One fixed package, agreed brand and domain surfaces, named responsibilities, prerequisites, and an acceptance matrix.
Full White Label
Broader brand, market, reporting, integration, and operating requirements — assessed after the first package proves out.
Enterprise
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.
11 · FAQ
Clear before the contract.
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 first-line 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 option, taxes, refunds, market law, and sustainable usage economics. The page does not grant unrestricted pricing rights.
Who provides support?
Your team handles first-line onboarding and customer communication. VUST handles second-line product support and coordinates third-line provider or infrastructure escalation. No public response-time or uptime SLA applies unless contracted.
What does the 14-day launch include?
An accepted fixed package: agreed brand and domain configuration, selected supported tools and surfaces, content, usage controls, monitoring, support handoff, QA, and a controlled launch. Custom platform work is outside that promise.
Is source code included?
No. Partner Launch does not include source-code ownership, repository access, or a partner-specific code fork.
What is the next step?
A structured launch brief or a fit conversation. We assess the audience, the customer job, and the channel, then state plainly what is included, planned, optional, or not supported. Opening a conversation commits you to nothing.
Technical and commercial details
When does the 14-day timeline start?
After the signed scope, cleared setup payment, approved assets, DNS and other access, legal and business details, tool and package decisions, support contacts, credentials, and an acceptance owner are complete.
Can we request new tools?
Yes, but they are assessed as an add-on or a later phase. A request is not a promise that the tool is available, safe, economical, or inside the original timeline.
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 and 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 and 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 service 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.
Next step
Bring the audience. We bring the product.
The launch brief takes about five minutes: who you serve, the customer job you want to package, how customers will arrive, and your scale and budget range. We reply with an honest fit assessment — included, planned, optional, or not supported.
Fixed scope · Qualified partners · No commitment from a conversation
The brief asks for
Your audienceCurrent businessThe customer jobDistribution channelWeb / Telegram surfacesApproximate scaleBudget rangeLaunch timeframe