Fundamentals
Understand how the resources you deploy on Azion connect into one chain that serves traffic, how your account is organized, and where to start.
A web platform is a service you build on instead of a stack you operate. You write the application and describe how it should behave, and the provider runs it on infrastructure it owns, filters the traffic that reaches it, and shows you what happened to every request. The servers, the routing, and the scaling stop being your work.
Azion Platform is that service on Azion’s globally distributed infrastructure: the integrated technology and the interfaces where you build, secure, and scale applications, which includes operating and monitoring them. Use Azion Platform to run an application close to its users, block the traffic it should not receive, store the data it reads, and watch every request it serves.
Platform resources topology
Everything that serves traffic on Azion is a set of Platform Resources bound to one another, with what you enable listed inside the resource it attaches to. The diagram shows how they connect: what the workload binds, what each resource holds, where the application fetches from, and what a function can call. Select a card to open it and read what it is and what it holds.
- A workload receives the traffic for its domains. It holds the domains and the certificate from Certificate Manager, and it binds, side by side, a firewall, an application, and a custom page set.
- A firewall inspects each request before the application. You apply a WAF rule set, Bot Manager, Network Shield lists, and functions to it. DDoS Protection is always on, with or without a firewall.
- An application serves the content. Its Rules Engine applies behaviors, Cache answers repeat requests from a stored copy, Image Processor resizes images on the way, and Functions run your code in the request path.
- A custom page set replaces the default error responses with pages you control.
- When the cache cannot answer, the application fetches the content through a connector: an HTTP connector reaches your origin server, and a storage connector reads an Object Storage bucket. Load Balancer and Origin Shield are enabled on the connector.
- Functions call what the Store card holds, SQL Database, KV Store, and Object Storage, and what the AI card holds, AI Inference.
To move an application that already runs elsewhere onto this chain, refer to Migrate to Azion.
Interfaces
You create and manage every resource in the chain through the Platform’s interfaces. Azion Console is the web interface, Azion CLI drives the same operations from a terminal, the Azion API exposes them over HTTPS for integrations, and the Azion Terraform Provider declares them as code. Azion’s catalog groups what you enable on those resources into four categories: Build, Store, Secure, and Observe. For the request path and the table of what each resource holds, refer to How Azion works.
Your account
Everything you build on Azion lives inside an account. The account holds the resources, the people who work on them, the billing profile, and the security controls that apply to every sign-in. Each person signs in as a user of the account. The account owner creates teams and sets their permissions, and each user belongs to one or more teams that decide which resources they can view or change. A Group account also holds client accounts, each with its own owner. Usage is metered per account and becomes an invoice on the Billing page.
If you do not have an account yet, refer to Create an account. For the full model, refer to Accounts, teams, and users.