Find the decision-level answers first. For account-specific questions, contact the team and include the workspace or app you are asking about.
Getting Started
What is TopoloOne?
TopoloOne is the entry point for Topolo apps, workspace access, billing, and app discovery. It gives a team one place to start work instead of sending people through separate product entry points.
How does TopoloOne work?
You sign in once, choose the apps your workspace needs, and manage access from the TopoloOne surface. The app catalog can include Topolo-built apps and approved third-party apps.
What applications are included?
The catalog changes as new apps are approved. Current app categories include communication, customer operations, documents, scheduling, automation, and administration.
How is this different from using applications directly?
Direct app links are useful once a workflow is established. TopoloOne is the shared launcher and control surface for finding apps, signing in, managing seats, and keeping workspace access consistent.
Billing & Pricing
How much does TopoloOne cost?
The pricing page shows the current public pricing and plan options. Use that page as the source of truth because live offers can change.
What does the workspace subscription include?
One annual subscription per purchased human seat includes every current first-party Topolo app, agent access through MCP, CLI and APIs, shared identity and permissions, and the platform audit trail. Installing another included first-party app does not add a licence charge. Preview labels describe app readiness.
Per-app pricing remains available for future premium first-party apps. Paid third-party apps are priced by their developers. External model, messaging and other provider costs require a separate spending budget. There is no Topolo surcharge for using your own model key.
How does billing work for teams?
Buy seats for the people on your team, with a minimum of one. Agents, API keys and service identities do not add paid seats. Pending invitations and unused purchased seats remain part of your annual commitment.
How do agents and usage affect the bill?
Seats are purchased for humans. Agent identities, model choices, API keys and parallel agent processes do not add seats. Usage is attributed to the organization, with per-user and per-agent detail for monitoring and budget controls.
Included usage is shared across the organization. The usage rate card shows each unit, monthly allowance, reset period and additional-usage price. After trial, usage above included allowances is charged automatically at the version accepted at checkout. Authorized billing administrators can review consumption and configure alerts and limits. Alerts warn; a hard spending limit stops further chargeable work. Trial usage stops at its included limits. Customer-funded provider usage is billed by that provider and is not charged again as a Topolo model fee.
Is there a trial or setup fee?
The workspace starts with a 14-day, card-required trial. No subscription charge is due until the trial ends. Cancel before it ends to avoid the annual charge. Guided self-service onboarding has no implementation fee; ordinary support is included.
Can I change my seat commitment later?
Seat additions require confirmation of the prorated annual charge. Reductions apply at the next annual renewal. Cancellation stops renewal under the terms shown at checkout.
What accounting features are included?
The ledger is included. Statutory payroll, tax filing and country-specific e-invoicing are outside the first-party launch commitment. Use a suitable extension or export where local requirements apply.
Do you offer refunds?
Refunds are handled case by case. Contact support with the workspace, subscription, and reason for the request.
What payment methods do you accept?
Card checkout is the standard path. Contract or invoice-based billing can be discussed for larger deployments.
Security & Privacy
How secure is TopoloOne?
TopoloOne is built around centralized sign-in, scoped app access, and workspace-level administration. Sensitive requests should always go through the authenticated app or the official contact channel.
Where is my data stored?
Data location depends on the app and service involved. If your team has a regional or compliance requirement, raise it before rollout so the right deployment path can be confirmed.
Who has access to my data?
Access is limited to the app, workspace permissions, and operational support needs. Never send secrets, credentials, or private customer data through unauthenticated forms.
How do you handle authentication?
TopoloOne uses Topolo sign-in for the marketing and workspace flow. App-specific access is scoped through the platform so users do not need a separate identity flow for every app.
Are you GDPR compliant?
For privacy or data-processing questions, contact the team with your organization, jurisdiction, and intended use case. The legal pages explain the current public terms and privacy posture.
Individual vs Team Features
What's the difference between individual and team plans?
Individual use is for a single person getting started. Team use adds shared workspace administration, seat management, and coordinated app access.
Can individual users collaborate with others?
Some apps support sharing or collaboration directly. A team plan is the right path when billing, users, and permissions need to be managed centrally.
How do team permissions work?
Workspace admins control who has access to the workspace and which app capabilities are available. Specific app permissions depend on the app being used.
Can I start with an individual plan and upgrade to a team plan?
Yes. Start small, then move to a team setup when shared billing and administration become useful.
How many users can I have on a team plan?
Seat limits depend on the selected plan and deployment model. Contact the team if you expect a larger rollout.
Technical Support
What kind of support do you provide?
Support starts through contact, app-specific help surfaces, and the public docs where available. Include the app, workspace, and what you were trying to do.
What are your support hours?
Response coverage depends on the plan and the type of issue. Critical production concerns should say so clearly in the subject and include the affected workspace.
How quickly do you respond to support requests?
Support triage depends on plan, severity, and available context. Clear reproduction steps and the affected app usually lead to the fastest response.