Everything in one place.
Only the details you want to open.

Start with one working sale instead of learning every menu at once.

• Guided setup: a saved path through panel connection, payment method, email sender, first plan and storefront publishing.
• Private workspaces: each reseller keeps their own customers, orders, connections, settings and operational records separate.
• Dashboard & today’s work: a business overview and shortcuts into the tasks that need attention.
• Task-based menus: Customers, Sales, Services, Billing, Store, Support, Marketing and Settings, with collapsible navigation and menu search.
• Record search & alerts: find customers, orders, services, plans and panels; review notifications from the top bar.
• Help that stays out of the way: page-specific guides you can stop and reopen, plus a searchable, detailed user guide.
• Responsive appearance: mobile layouts, light/dark choices and saved appearance settings. First visits start in light mode.
• Fictional working demo: explore without registering; sample data and demo changes reset automatically.

Completing setup proves the settings are saved. It does not by itself prove payment, remote provisioning or inbox delivery.

• Saved panel connections: recognizable names, connection URLs, encrypted credentials, compact card/list views and individual management tools.
• “What Panel Do I Have?”: checks a public login address for recognizable panel-software markers without asking for a password. It can return an unknown result instead of guessing.
• Connection testing: distinguish a successful login from an unreachable host, rejected credentials or missing permissions.
• Named catalog discovery: load available packages, channel groups and package-specific default selections without hunting for raw IDs.
• Actual trial discovery: supported browser connectors inspect trial-specific forms and metadata. A paid package is not automatically turned into a trial.
• Background catalog refresh: refresh all accessible package defaults, preserve the previous saved catalog if discovery fails, and review warnings.
• Saved lineups: reuse named channel-group selections for the correct panel; mappings remain panel-specific.
• Connection health: test results, catalog counts and reported credit balances where the provider supplies them. N/A is not a zero balance.

Integration availability

• First-release priorities: NXT, XUI browser and Xtream UI browser, including the RedTeam connector.
• Assisted: MegaOTT and native XUI API connections need extra validation. MegaOTT’s shared catalog and templates are not a verified complete account-specific live catalog.
• Unverified catalog entries: Activation Panel, Argon, Dream 4K, GoldenOTT, OneStream, Strong 8K, TiviOne, TV Plus Panel, TV Pro (NETTV), Ultra 8K, V12 / MaxOTT and Xtream Masters. Being listed is not a claim of a proven lifecycle.

Your upstream account controls the packages, trials, permissions and credits you can use. APP does not supply a panel account, service content or credits, and cannot make an unavailable trial appear.

• Quick setup from a panel: select discovered packages, selling terms and prices to create draft offers, then review and publish them.
• Manual plan creation: create a customer-facing plan with a destination panel/package, duration, connection count, login type, channel lineup, retail price and currency.
• Locked fulfillment: buyers cannot change your underlying package, term, connection allowance or channel selection at checkout.
• Cross-panel service defaults: reuse settings such as “one month, three connections” with separate lineup mappings for each panel. A default is not a package or selling price.
• Compact plan management: list, panel and category views; search and status filters; edit, copy, ordering and publication controls.
• Drafts & archives: keep unfinished offers private and retire an offer from normal use without confusing it with service termination.
• Trials: clearly identify free or priced trials using an eligible upstream package and the panel’s actual limits.
• Categories & discounts: organize the public catalog and apply eligible promo-code rules without unlocking service choices.

A copied plan still needs a valid destination mapping. Panel credit cost and your customer’s selling price are separate amounts.

• Hosted storefront: your own published offer catalog, without requiring a separate website, WordPress or WHMCS.
• Individual plan links: share a specific offer by email, chat or a button on your existing website.
• Storefront designer: business identity, branding, colors, responsive theme presets and saved light/dark appearance.
• Preview & publishing: review the buyer view before making the storefront public. Offer publication is a separate control.
• Pages & FAQs: seller-managed informational pages, frequently asked questions and knowledge articles.
• Offer presentation: plan name, price, term, connections and included lineup, with search and category organization.
• Customer entry points: checkout, sign-in, account, private order status and support links connected to the same seller.
• Custom-domain setup surface: request and manage a hostname where entitled. DNS verification and working TLS/routing are required before it is live.

The optional native WordPress connector is planned. Existing sites can already link to hosted offers. A pending custom domain is not an activated one.

Your customer pays through the gateway you connect. Your separate APP subscription does not route that customer payment through the platform owner’s account.

• Choose your included gateway: new workspaces choose their allowance; no payment method should be selected for them by default.
• Stripe: supported existing-account connection or direct-key setup, hosted checkout and verified payment notifications.
• Other gateway integrations: PayPal, Square, Cash App Pay through Square, NOWPayments and BTCPay Server have their own configuration and payment-verification paths.
• Connection methods: OAuth/connect only where the provider and platform configuration allow it; credential setup remains available where supported. Not every provider has a ready one-click sign-in.
• Manual-transfer methods: Interac e-Transfer and Wise require seller confirmation of received funds before fulfillment; they are not instant automatic payment verification.
• Webhook guidance: workspace-specific notification URLs, credential fields and setup instructions; keep live and sandbox credentials separate.
• Gateway management: configure, refresh or disconnect a connection, review its readiness and recorded order outcomes.
• Customer wallet top-up: signed-in buyers add funds through the seller-owned Stripe flow; verified payments credit an idempotent ledger and show the portal balance.
• Spend store credit: use an available wallet option for a later purchase or renewal within that seller’s workspace.

Provider approval, region, enabled capabilities and platform readiness can limit a gateway. Private testing is Stripe-first; other listed methods need their own successful end-to-end check before use. A wallet top-up alone does not buy or renew a service.

• Manual sales: create a customer order using a locked plan and an optional service default, with source and internal notes.
• Payment-to-provisioning handoff: a verified payment queues the supported remote action. A checkout return page alone is not treated as payment proof.
• Order queues: see pending, ready-to-deliver, failed and active records without mixing payment status with service status.
• Controlled retries: read the failure and retry through the operational tools; idempotent handling helps prevent duplicate fulfillment.
• Service records: destination panel, package, remote account ID, service credentials, term, connections, lineup and expiry.
• Existing-line linking: record the correct upstream account ID and login for a line that already exists rather than creating another.
• Supported lifecycle actions: create, renew, suspend, reactivate or terminate where the connector and upstream permissions support the action.
• Panel changes: explicitly map a destination and existing line when switching; no silent automatic cross-panel move.
• Private delivery: protected order/access pages and service-ready messages through the seller’s configured sender.
• Traceable actions: operational status and audit records help identify whether payment, the remote panel or email delivery failed.

A successful connection test is not a successful create or renewal. Validate the real remote account and expiry, not just a green queue status. Upstream actions may consume credits.

• Customer invoice list: search and review invoices, amounts, currency, payment state and linked customer/service records.
• Receipts & private order status: let buyers check the specific payment and fulfillment result.
• Renew the existing service: use the linked renewal flow so verified payment extends the intended remote line instead of creating an unrelated order.
• Trial-to-paid flow: eligible trial services can use their offered paid upgrade/renewal route.
• Autopay where supported: recurring provider billing and billing-management links remain distinct from manually paid renewals.
• Scheduled reminders: due-date notices through the reseller’s sender. The reviewed service schedule targets 7, 3, 1 and 0 days before due, with a default 9:00 AM America/Chicago schedule.
• Renewal queue: review upcoming services, billing state and failures from Services and the customer profile.
• Manual payment review: confirm a transfer before marking it paid and queuing the supported service action.

Reminder timing depends on the configured timezone, scheduler, queue and tested sender. Editing a due date does not itself prove renewal. Invoice creation, receipt delivery and panel renewal are separate steps.

• Customer directory: a simple name-and-service overview; open the person to see the detail.
• Email-required records: customer creation requires an email. Saving a contact address is not automatically a portal invitation.
• Customer profiles: Overview, Services, Orders & invoices, Tickets, Emails, Activity and Wallet.
• Add subscriptions: start a service order from the customer profile using the intended plan and panel mapping.
• Customer groups: seller-defined groups, assignment and filtering.
• Basic customer CSV import/export: current directory tools are separate from the future full service-migration toolkit.
• Customer portal: a buyer account for this seller, with order/access links, supported billing links, wallet and support tickets.
• Separate logins: the portal password opens the website; the upstream service username/password or device MAC opens the service.
• Customer assistance: authorized seller tools for inspecting a buyer’s account and resolving the linked order or service.

A reseller is the business running a workspace; customers are the buyers inside it. Accounts with one reseller do not grant access to another reseller’s portal.

• Your own email sender: SMTP credentials, provider presets, from name/address and optional reply-to for business or domain mailboxes.
• Sender testing: send a test, review the actual result and confirm it reaches the inbox before relying on automated messages.
• Transactional notices: supported service-ready, payment and renewal communications remain linked to the relevant customer or order.
• One-to-one & campaigns: compose a message, choose its type and eligible audience, save a draft or queue delivery.
• Scheduled sending: schedule later rather than immediately queuing a campaign.
• Delivery history: campaign history and recipient-level sent/failed records; a queued email is not proof of inbox receipt.
• Marketing controls: eligibility and unsubscribe handling separate promotional messages from service notices.
• Promo codes: create seller-controlled discount rules and usage/eligibility limits.
• Basic referrals: referral records and current attribution views, separate from future multi-level rewards.

Customer mail uses the reseller’s configured provider, not the platform owner’s mailbox as a fallback. Gmail OAuth simplification is still being worked on; don’t assume a Gmail sign-in button is already ready. Provider sending limits and delivery policies still apply.

• Customer tickets: buyers open conversations in their seller’s portal; the seller replies and tracks the ticket state.
• APP support: a separate private reseller-to-platform support channel, not the customer ticket inbox.
• Reports: current payment/revenue and operational summaries, separate from future accounting or cohort analytics.
• Abandoned checkouts: review captured incomplete checkouts; this is not an automatic win-back campaign engine.
• Service status: review connection/service health and supported status surfaces.
• Staff & workspace management: manage authorized staff/team access while retaining workspace boundaries.
• Account settings: profile, notifications, password/security tools and supported two-factor/passkey controls.
• Secret protection: encrypted saved credentials, protected operational access and audited sensitive actions.

Tickets are the working support route. Live chat, a specialized staff credential vault and expanded accounting/risk tools remain future modules. Never include passwords or payment secrets in a support ticket.

The tools above and the number of connections are different things. These are the current pre-launch pricing and allowance previews, not a public signup offer.

• Standard platform license: the main pricing preview lists a $199 one-time business license, separate from monthly capacity.
• Extra payment gateways: current preview price is $25.00 each beyond the included allowance; unlock does not supply a provider account or its credentials.
• APP subscription page: see platform billing and pay an available monthly bill manually when not using autopay.
• APP-fee reminders: separate from the invoices your customers pay to you.
• Overdue APP access: after the configured 24-hour grace period, APP access is suspended until payment is verified. This is not an instruction to suspend all remote customer lines.
• Invited test access: the owner can grant temporary feature/capacity access without collecting a payment. The grant’s actual expiry governs access.
• Owner-only administration: dedicated reseller directory, invitations, temporary grants, panel inspection, support inbox and protected platform controls. These are not ordinary reseller permissions.

All-access means currently available features and the granted capacity—not unfinished modules, upstream credits, payment fees, provider approval, unlimited email or guaranteed support for every panel. See the main pricing preview.

The Add On Modules catalog lets resellers see future ideas and save interest. These entries are not installed or activated features, have no committed release date, and do not become live simply because you have Gold or a test grant.

Messaging & sales channels

• Discord notifications: order, renewal and support alerts; role automation.
• Discord selling bot: browse, buy, renew and request support inside Discord.
• WhatsApp messaging: approved business messaging for reminders and confirmations.
• Telegram selling bot: plan browsing, payment links, renewals and tickets.
• Live chat: storefront conversations, staff inbox and offline messages.

Automation & protection

• Invoice pay links: expanded single-invoice link and expiry controls beyond current supported renewal payment.
• Panel failover: explicit backup mappings and audited outage rules.
• Advanced trial protection: additional device, network and email-risk review.
• Gateway statement branding: provider-supported descriptor controls—not hidden merchant identity.
• Checkout risk signals: suspicious-checkout review and reversible rules.
• Staff credential vault: specialized secret sharing and role-based audit.

Marketing & storefront growth

• Upsell campaigns: targeted longer terms, connections and approved extras.
• Advanced page builder: reusable blocks, ordering and mobile previews.
• Store translation: seller-reviewed storefront and email languages.
• Customer invitations: tracked invite groups and conversion reporting.
• Knowledge base packs: installable, editable article collections.
• Referral Plus: milestones and expanded reward levels.
• Loyalty & rewards: points, renewal streaks and redemption controls.
• SEO toolkit: metadata, indexing and content checks.
• Churn recovery: controlled win-back sequences after expiry.
• Meta ads measurement: seller-owned tracking and consent-aware purchase events.
• Checkout add-ons: compatible extras without unlocking fulfillment choices.

Operations & new service types

• Accounting & expenses: cost categories, operating expenses and profit/loss exports.
• Panel credit tracking: balance history, low-credit alerts and forecasts.
• Additional storefront domain: another verified hostname for the same catalog.
• Google marketing tools: Analytics, Tag Manager and Ads conversion connections.
• Guided data import: mapping, duplicate checks and pre-import validation beyond the current directory import.
• Installable web app & push: home-screen installation and permission-based notifications.
• WHMCS migration toolkit: read-only source export and customer/product/invoice/service mapping.
• Advanced analytics: cohorts, retention and deeper performance reporting.
• Public channel lineup: a searchable, seller-approved lineup with logos and scheduled refresh.
• Tax-ready invoices: registration/rate rules and invoice tax breakdowns.
• Advertising workspace: campaign notes and performance views.
• VPN service automation: a separately verified provider adapter and lifecycle.
• Media-server integrations: Plex, Jellyfin and Emby setup surfaces remain gated/assisted, not a verified automatic selling workflow.
• WordPress connector: planned native placement for an existing site; hosted plan links already work without it.

Current included module entries—wallet top-up, storefront themes, customer groups, email-first checkout and guided setup—are covered in the sections above. They are not extra roadmap promises.