Can we buy only one product?
Yes. Each product can be bought on its own. Spot Suite keeps the shared Environment, identity, billing, and audit layer ready if you add more products later.
FAQ
These answers cover the public buying and setup path. Product-specific contracts, residency scope, and regulated workflows still need confirmation before production use.
Buying and setup
Yes. Each product can be bought on its own. Spot Suite keeps the shared Environment, identity, billing, and audit layer ready if you add more products later.
The trial form only shows products that are marked direct-purchase ready in the shared catalog. Other products start with a scoped activation so the Environment and product access are correct.
Some offers are prepared for Azure Marketplace or private-offer workflows. If procurement needs Microsoft Marketplace, contact us before rollout so the subscription path and tenant attachment are clear.
Compliance and security
Spot Suite can support DORA work by keeping ICT supplier, identity, access, cloud, transfer, and audit records exportable. It does not replace the customer DORA programme, legal analysis, or supervisory submissions.
We can scope HIPAA-aware workflows where access controls, audit trails, retention, regional data handling, and contract terms need review. Do not send protected health information until that scope is agreed in writing.
Use the security page or email hello@spot-suite.com. Include the affected route, Environment, steps to reproduce, timestamps, and the likely impact.
Data residency and operations
Residency options for EU, Asia, and US setups are scoped during Environment setup. The exact region, product coverage, support process, and transfer constraints need to match the customer requirement.
It is the customer-owned operating boundary for identity, product access, audit history, billing state, and provisioning decisions across the selected Spot Suite apps.
Yes. Spot Suite is designed around Microsoft Entra OIDC, MFA, passkeys, roles, and product access controls. Customer-side SSO details are scoped during rollout.
Still unsure?
A useful request names the product, the business owner, the systems involved, the target region, and the compliance question you need answered.