Use Cases
Each use case is a validated design that shows how Azion products combine to solve it: the components, the flows, and the decisions behind each one.
All use cases
Every use case, grouped by the solution it serves.
Build and run applications
Build and run marketing websitesDeploy a marketing site from GitHub on every push, serve it from Object Storage through Cache, and purge it after each deploy.Read the use case Deploy full-stack applications globallyDeploy a Next.js application from GitHub so its pages render in a function that reads SQL Database, and its build assets come from a bucket.Read the use case Build REST and GraphQL APIsRun an API as one function that reads SQL Database, writes through the Azion API, caches list responses, and reports latency and errors.Read the use case Build event-driven APIsVerify payment webhooks in a function, filter repeated events with KV Store, and queue each event in Upstash QStash before answering.Read the use case Modernize a monolithic application without a rewritePut an application in front of a monolith, move one route at a time to a function on Azion, and roll a route back by turning its rule off.Read the use case Build e-commerce storefrontsCache the catalog pages of a store you run, keep cart and checkout dynamic, and purge product pages when the catalog changes.Read the use case Deploy frontend applicationsServe a single-page application from Azion and send its API calls to the backend you already run, under one domain.Read the use case Run multi-tenant SaaS applicationsServe every tenant of a SaaS product from one function that resolves the tenant from the hostname, with configuration in KV Store and data in SQL Database.Read the use case Migrate an application to a new origin without downtimeMove an application's traffic from an old origin to a new one in weighted steps, watch errors on each origin, and roll back by changing one address.Read the use case
Improve application performance and reliability
Accelerate websites and APIs with a CDNPut an application in front of your origin to cache static files and pages with Tiered Cache, pass API calls through, and accept only Azion at the origin.Read the use case Keep an application online when an origin failsGroup a primary and a standby origin in one connector with Load Balancer, and answer with your own error page when neither origin can serve.Read the use case Optimize images for websites and mobile appsResize and convert the images on your origin on request with Image Processor, cache every variant, and request a fixed set of sizes from your pages.Read the use case Monitor website and API performanceCollect page load measurements from real visitors with Edge Pulse, query them per page, and compare them with what Azion served for the same domain.Read the use case Route users to regional originsSend each request to the origin of the user's region with geolocation rules, and fall back to another region only where your rules allow it.Read the use case
Build and run AI workloads
Build and run customer support AI assistantsAnswer customer questions from your own documentation, with passages retrieved by vector search and an answer generated by a model on Azion.Read the use case Add AI features to existing applicationsAdd a summarization API route to an application you already run, with a function that calls a catalog model on AI Inference and caches results.Read the use case Build AI agentsRun a tool-calling agent loop in a function on Azion, with a third-party model, state between steps, human approval, and a history of every task.Read the use case Deploy remote MCP serversExpose an existing API to AI agents as MCP tools from a function on Azion, with WAF and a rate limit in front and a log line for every tool call.Read the use case Govern access to multiple AI modelsPut one gateway function in front of AI Inference and a third-party provider to authenticate teams, route by policy, fall back, cache, and log every call.Read the use case
Secure applications and networks
Protect web applications from OWASP Top 10 and zero-day attacksPut a firewall in front of a web application, so network lists, WAF, and Bot Manager run in one policy and the origin accepts only Azion's traffic.Read the use case Protect public APIs from abusePut a firewall in front of a public API, so WAF, a token check, Bot Manager, and a rate limit per client run before any request reaches the API origin.Read the use case Block account takeover on login and checkout flowsScore every request to login, signup, and checkout for automation, then challenge or deny it before it reaches the identity system or the payment flow.Read the use case Block attackers automatically from SIEM detectionsLet a SIEM or SOAR playbook write the offending addresses to a network list that a firewall rule already denies, with an expiry on every entry.Read the use case Screen file uploads for malicious contentRun a firewall function that sends each upload to a model on AI Inference, deny the files it flags, and block their senders with a network list.Read the use case Prepare regulated web applications for security auditsEnforce HTTPS, filter attacks, restrict access by country and address, and export every security event to a destination the team keeps for its audits.Read the use case
Deliver media and streaming content
Stream live events to large audiencesPush a live stream from your encoder to Live Ingest and deliver it as HLS through an application that caches playlists and segments for every viewer.Read the use case Deliver an on-demand video libraryStore an encoded HLS video library in Object Storage and serve its playlists and segments through an application with Cache and Tiered Cache.Read the use case
Also useful: Guides, How Azion works, use cases llms.txt