Managed white-label operating model
Last updated: 1 July 2026. This page is a plain-language business guide, not legal advice. Any paid platform should use an attorney-reviewed services agreement and statement of work.
The default white-label offer is fully managed. MarkVizion maintains the shared platform codebase, hosting setup, deploy pipeline, security posture, vendor integrations, and core updates. The platform owner controls the brand direction, content, member experience, city purpose, public copy, launch calendar, and business approvals.
The owner does not need to set up hosting, source-code repos, serverless functions, API keys, email credentials, or payment infrastructure for the standard managed plan. An enterprise or self-hosted arrangement can be negotiated separately, but it requires a separate contract, higher setup cost, dedicated vendor accounts, security review, and migration planning.
Paid platforms should use a written agreement that can include a build or setup fee, monthly Platform Care, optional Managed Operations, transaction/platform fees, and pass-through costs for unusual storage, bandwidth, email, AI, livestreaming, SMS, domains, premium plugins, or third-party overages.
If monthly Platform Care is not paid, MarkVizion can pause non-emergency updates, owner-requested changes, custom support, paid modules, or eventually public access after notice. Safety, legal, security, and data-preservation needs may still require limited emergency action.
Under the managed plan, MarkVizion controls production hosting, deploys, function routing, CDN/cache behavior, platform-level API keys, and vendor credentials. This keeps updates centralized and reduces security risk.
Owners may use a platform subdomain or bring a custom domain. For custom domains, the owner must keep registrar/DNS access and cooperate with DNS verification, SSL, and sender authentication. Owners should not receive raw production hosting access or secret keys unless an enterprise agreement requires it.
Commerce features require separate payment terms. Owner payouts should use a connected payment account, such as Stripe Connect, when owner commerce, ticketing, memberships, or marketplace revenue is enabled. The owner remains responsible for taxes, fulfillment, refunds, customer support, chargebacks, shipping, and legal obligations for what they sell unless a managed-operations agreement says otherwise.
Each platform should have one or more owner notification emails. These can receive member signups, contact forms, bookings, sponsor leads, purchases, moderation reports, system notices, maintenance windows, deploy summaries, and major feature updates.
The owner can request routing rules, such as sales leads to one address and moderation reports to another. If the owner wants mail to send from their own brand domain, they must cooperate with SPF, DKIM, DMARC, and other deliverability records. Platform email is for operational and consent-based communication, not spam, deceptive messages, or purchased lists.
Core platform updates roll out centrally, including security fixes, bug fixes, accessibility improvements, mobile/controller compatibility, performance updates, games, profile systems, dashboards, and infrastructure changes.
Owner-specific changes can happen through dashboard edits, written update requests, or paid sprints. MarkVizion can decline, delay, or modify changes that create legal risk, security risk, vendor-policy risk, performance problems, or breakage for other owners.
The owner keeps ownership of their brand assets, logos, names, uploaded media, product materials, copy, and approved business content. MarkVizion keeps ownership of the underlying software, systems, game engines, admin tools, templates, shared modules, infrastructure patterns, and reusable methods unless a signed agreement says otherwise.
Owners can receive appropriate reports and exports for their own platform. They should not receive raw infrastructure access, cross-platform user data, private data from other owners, passwords, secret keys, or unrelated analytics.
The owner is responsible for rights clearance, brand accuracy, content legality, product claims, regulated-industry requirements, privacy requirements, and the materials they ask to publish. MarkVizion can remove, hide, suspend, or restrict content, accounts, modules, commerce, or platform access if there is suspected infringement, harassment, fraud, abuse, illegal content, unsafe conduct, unpaid fees, security risk, or harm to users or the platform.
If an owner cancels or materially breaches the agreement, MarkVizion may disable paid modules, pause updates, remove public access, or archive the platform after any required notice period. On exit, the owner can request reasonable exports of their brand assets, owner-provided content, reports, and legally available member/contact data. The owner does not receive MarkVizion source code, shared platform systems, private credentials, or other owners' data unless a signed agreement grants those rights.
Managed platforms may depend on vendor rules for hosting, email, payments, AI, media, and analytics. Useful references include Stripe Connect terms, Twilio SendGrid email policies, Netlify acceptable-use rules, and OpenAI business/API policies. These vendor terms can change and should be checked during contract review.