Understand the platform
without guessing at deployment details.
Answers describe the public Thonem product model and clearly separate it from project-specific contracts.
Is Thonem a hosted SaaS storefront?+
Thonem is presented here as Brightery’s custom commerce infrastructure. The exact deployment model, modules and integrations depend on the implementation project.
Can Thonem integrate with payment and shipping providers?+
Thonem projects can use adapter-based payment, shipping and business-system integrations. Provider availability and exact capabilities must be verified for the deployed project.
Does the public website health endpoint monitor checkout or payments?+
No. The included health endpoint intentionally reports only the public website overlay files. Commerce, database, queue and provider health require application-specific monitoring.
Can an existing commerce system be modernized gradually?+
Yes, the architecture guidance favors isolating domains and adapters so compatible parts can be upgraded in phases rather than assuming a full rewrite.
Does Thonem have one fixed public API contract?+
This website does not publish a universal production API contract. Exact endpoints, schemas, authentication and webhook rules are project-specific unless separately documented for a deployment.
How are website releases protected from the live application?+
The website stays inside dedicated /explore/ and /_thonem-site/ namespaces, and the release tooling validates those boundaries before replacement.