What do you want to do, and which service fits
| I want to… | Use | Code needed |
|---|---|---|
| Have a website for my shop, company or portfolio | Website (drag and drop) | No |
| Take orders, sell or take bookings on my website | Business Apps on a website (Starter and up) | No |
| Use email like [email protected] | No | |
| Give guests Wi-Fi with a sign-in page and logs | Wi-Fi Hotspot | No |
| Store files, images, videos or backups | Object Storage | Not required (you can upload in the Console) |
| Run heavy work in the background so the site stays fast | Queue Service | Yes |
| Put up a site built with React, Vue, Astro and so on | Static Web | Yes |
| Run my own app or API | Containers | Yes |
| Keep data in tables | Managed Databases | Yes |
| Keep sessions, caches or job queues | Managed Cache | Yes |
What every service shares
- A Project is the box that keeps services together. Each Project has its own plan, wallet, members and VPC (see Projects and inviting your team).
- You choose a Region when you create a website or service, so free addresses include the region name, such as
name.sites.region.thailandhosting.com. - Costs: plans and cloud services are charged to the Project’s wallet. See what you’ve used in Quotas & usage.
- Access: members only see and change the Projects they’re invited to, within the role they’re given (see People and access).
You don’t need everything on day one. Start with a website and add services when your business needs them. New services in the same Project can talk to each other right away.