Documentation
Documentation for both the public product experience and the platform behind it.
The docs home should help customers, operators, and evaluating teams move through launches, billing, domains, support, workspace access, and admin operations without guessing where the truth lives.
Quickstart
Start where most users need help first.
Use the docs home to orient people quickly around product launch, billing, and the customer workspace.
Launch your first app
Understand app selection, launch review, and the product-led onboarding path into the customer workspace.
Understand wallet and invoices
Learn how workspace funding, launch billing, renewals, invoices, and transactions fit together.
Connect domains and go live
Follow the path from fallback domains to custom domains, SSL, and primary-domain behavior more confidently.
Doc categories
Grouped around the actual surfaces people use.
The docs structure follows how Stackelio works in the product, not just how the codebase is organized.
Getting started
Launch your first managed app
Understand account setup, workspace onboarding, and the first launch flow from a product-led perspective.
Billing
Wallets, launches, renewals, and invoices
Learn how Stackelio explains funding, launch billing, recurring renewals, and finance activity to customers and operators.
Domains
Custom domains, SSL, and routing
See how temp domains, custom domains, verification, SSL state, and primary-domain behavior fit together.
Support
Support flows for customers and operators
Use customer tickets, attachments, internal notes, assignment, and escalation-aware operations more confidently.
Workspace
Shared access and team collaboration
Invite teammates, manage members, and understand how shared access works across services, billing, and support.
Operator guides
Run the platform
A home for nodes, roles, reports, global settings, finance operations, and the admin control plane.
Help direction
Know when docs should answer the question and when a human conversation should start.
Good docs reduce support friction, but a strong public docs page should also direct people into onboarding or product conversations when appropriate.
Use docs for product understanding
Launch flow, workspace billing, domains, support, products, and operator surfaces all deserve clear guides.
Use contact for platform-fit questions
If the question is really about rollout strategy, managed app packaging, or operator needs, move naturally into contact.
Frequently asked
The questions people ask before they trust the platform.
Use the docs home to reduce uncertainty around the product and the platform story.
How do I pay for a launch?+
Launch review and wallet funding work together so the customer can understand what is charged immediately and what remains reserved or recurring.
How do renewals show up?+
Renewals are handled through invoices that can move through due, grace, suspension, and restoration states while remaining visible in the customer billing flow.
Can my team share access?+
Yes. Workspaces support members so services, billing visibility, and support are not trapped in a single-user account model.
Where do operators manage the platform?+
The admin control plane already supports nodes, clients, roles, reports, settings, tickets, wallets, and invoices behind the public-facing product.
Need more than docs
Use documentation to get oriented, then bring Stackelio into the deeper platform conversation.
The docs home now feels like part of a real product website instead of a flat placeholder page.