Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
31 commits
Select commit Hold shift + click to select a range
b07421e
docs(fundamentals): redraw the request path in How Azion works
marcus-souza-azion Nov 3, 2026
ac1f231
docs(fundamentals): rewrite the Fundamentals opening and simplify the…
marcus-souza-azion Nov 3, 2026
0c475ae
docs(fundamentals): align First deploy with the current Console and w…
marcus-souza-azion Nov 3, 2026
19431c3
docs(fundamentals): tidy Accounts, teams, and users
marcus-souza-azion Nov 3, 2026
877cb77
docs(fundamentals): match Account settings to the Console sections
marcus-souza-azion Nov 3, 2026
99e8954
docs(fundamentals): rename the User Profile section of Your settings …
marcus-souza-azion Nov 3, 2026
c7f613a
docs(fundamentals): name the platform and the Profile section in User…
marcus-souza-azion Nov 3, 2026
d14f938
docs(fundamentals): add Group accounts and rename the page to Groups …
marcus-souza-azion Nov 3, 2026
e124fe8
docs(fundamentals): replace the trial credit in Billing with the curr…
marcus-souza-azion Nov 3, 2026
3664298
docs(fundamentals): say that Account Lockout Policy is configured thr…
marcus-souza-azion Nov 3, 2026
7cceb0c
docs(fundamentals): say that User Session Timeout is configured throu…
marcus-souza-azion Nov 3, 2026
ac12f3b
docs(fundamentals): bring the Teams permissions table in line with th…
marcus-souza-azion Nov 3, 2026
b036740
docs(fundamentals): restructure HTTP status codes and fix the 500 red…
marcus-souza-azion Nov 3, 2026
1d77e6a
docs(fundamentals): give Multi-Factor Authentication a subject headin…
marcus-souza-azion Nov 3, 2026
6679c65
docs(fundamentals): close Social Login with related resources
marcus-souza-azion Nov 3, 2026
9167293
docs(fundamentals): put the Personal tokens fields in a table
marcus-souza-azion Nov 3, 2026
6b09c8a
docs(fundamentals): restructure Single Sign-On around its terms and g…
marcus-souza-azion Nov 3, 2026
a81bfae
docs(fundamentals): put the Account Lockout Policy settings in a table
marcus-souza-azion Nov 3, 2026
385044b
docs(fundamentals): put the User Session Timeout settings in a table
marcus-souza-azion Nov 3, 2026
1a3f89f
docs(fundamentals): turn the PCI compliance FAQ into subject sections
marcus-souza-azion Nov 3, 2026
56db009
docs(fundamentals): turn the SOC compliance FAQ into subject sections
marcus-souza-azion Nov 3, 2026
1003fad
docs(fundamentals): replace the shared responsibility image with a table
marcus-souza-azion Nov 3, 2026
08811df
docs(fundamentals): trim the Accounts, teams, and users related resou…
marcus-souza-azion Nov 3, 2026
1312e2a
docs(fundamentals): put the Your settings fields in tables
marcus-souza-azion Nov 3, 2026
e69620b
docs(fundamentals): put the Account settings fields in tables
marcus-souza-azion Nov 3, 2026
5b9c458
docs(fundamentals): close Activity history with related resources
marcus-souza-azion Nov 3, 2026
edc8b1e
docs(fundamentals): put the Groups and clients fields in tables
marcus-souza-azion Nov 3, 2026
034c616
docs(fundamentals): name the Teams permissions columns and close with…
marcus-souza-azion Nov 3, 2026
4b02e5a
docs(fundamentals): put the Users management fields in tables
marcus-souza-azion Nov 3, 2026
2ed4904
Merge remote-tracking branch 'origin/main' into review/mm-16289
egermano Nov 12, 2026
65630c7
docs(fundamentals): fix Console labels, the request diagram, and revi…
egermano Nov 12, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 34 additions & 14 deletions apps/docs/src/content/docs/en/pages/first-deploy/first-deploy.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -28,26 +28,26 @@ Three complete paths get you there. Pick one. They all end in the same place:

## Before you start

All you need is an Azion account. You can create one for free, and it does not ask for a credit card. Anything path-specific is listed in the path itself.
All you need is an [Azion account](https://console.azion.com/signup). You can create one for free on the Hobby plan. Anything path-specific is listed in the path itself.

## Deploy a template via Console

Templates are ready-made projects (e-commerce, blogs, APIs, full-stack SSR) that go live in a few clicks. You do not need any local tooling.

<DocCallout kind="note">Some templates are integrated with third-party services, so you may need to create accounts, generate tokens, or activate Azion products before deploying. Templates integrated with GitHub ask you to connect your account: select Connect with GitHub when prompted and confirm the connection in the window that opens. Each template's guide lists its specific prerequisites.</DocCallout>
<DocCallout kind="note">Templates with integrations or specific settings can ask for more input, such as accounts or tokens on other services. Templates integrated with GitHub, such as Astro Boilerplate, also need a GitHub account and ask you to connect it: select Connect with GitHub when prompted and confirm the connection in the window that opens. Each template's guide lists what it needs.</DocCallout>

<DocSteps>
<DocStep title="Access Azion Console." />
<DocStep title="Select + Create on the homepage." />
<DocStep title="In the modal, select Templates." />
<DocStep title="Browse and pick the one you want to start with." />
<DocStep title="Select the Astro Boilerplate template, or browse and pick another one." />
<DocStep title="Fill in the configuration page." />
<DocStep title="Select Deploy, in the bottom-right corner." />
</DocSteps>

Follow the deploy through the logs window. When it finishes, the page shows your application's name, its deploy logs, and its Azion domain. Some templates also create a function and apply pre-defined configurations to optimize your application's performance. The template's guide lists what is included.

### Test it
### Check the application

Copy the Azion domain from the confirmation page:

Expand All @@ -62,23 +62,43 @@ Open the same URL in the browser to see your application running.

## Import a project from GitHub

<DocCallout kind="info">You need a GitHub account and a repository using one of the supported frameworks.</DocCallout>
<DocCallout kind="warning">You need a GitHub account and a repository built with a framework that the **Preset** list carries: Next.js, Angular, Astro, Hexo, React, or Vue. Before you start, check your framework and its version in [Frameworks compatibility](/en/documentation/devtools/runtime/frameworks/frameworks-compatibility/): a framework or a version that Azion does not support can fail at build time.</DocCallout>

<DocSteps>
<DocStep title="In Azion Console, select + Create." />
<DocStep title="Select Import from Git." />
<DocStep title="Connect the Git account that owns the repository." />
<DocStep title="Pick the repository to import." />
<DocStep title="Name the application and check the build and deploy commands.">
<DocStep title="Name the application.">

Azion reads the commands from the repository, so both arrive filled in for a project it recognises — change them only if your build differs. The name becomes part of the deployed URL.
The Console fills **Application Name** with the repository name. The name must be unique on your account, and the storage bucket and the function of the project take the same name.

</DocStep>
<DocStep title="In Preset, select the framework of the repository.">

The preset sets the initial settings for that framework.

</DocStep>
<DocStep title="In Root Directory, keep the default value.">

The default value, `/`, applies when the project code is at the root of the repository.

</DocStep>
<DocStep title="In Install Command, enter the command that installs the project.">

For example, `npm install`.

</DocStep>
<DocStep title="Select Deploy.">

The **Deploy Log** panel shows the build until the Azion domain shows up.

</DocStep>
<DocStep title="Leave Protect with Azion Firewall off, or turn it on to deploy a firewall alongside the application." />
<DocStep title="Select Create and deploy, then follow the logs until the Azion domain shows up." />
</DocSteps>

### Test it
If the deploy fails, the page shows **Creation failed**, and the **Deploy Log** panel carries the details of the failure. For every field of the import, refer to [Import a project from GitHub](/en/documentation/guides/application-development/automation/import-an-existing-project-from-github/).

### Check the application

```bash
curl -I https://<your-azion-domain>
Expand All @@ -89,9 +109,9 @@ Open the Azion domain in the browser to see your application running. If you get

## Deploy with Azion CLI

<DocCallout kind="info">You need a local project that uses one of the supported frameworks, with its dependencies installed, or you create one from a template in step 3.</DocCallout>
<DocCallout kind="warning">You need a local project that uses a supported framework, with its dependencies installed, or you create one from a template in step 3. Before you start, check your framework and its version in [Frameworks compatibility](/en/documentation/devtools/runtime/frameworks/frameworks-compatibility/): a framework or a version that Azion does not support can fail at build time.</DocCallout>

<DocPrompt client:visible kind="line" title="AI Assistant">Set up the Azion CLI, log in, link this project to my Azion account or initialize one from a template, deploy it, and print the Azion domain once it answers 200.</DocPrompt>
<DocPrompt client:visible kind="line" title="AI Assistant">Follow the "Deploy with Azion CLI" section of https://www.azion.com/en/documentation/fundamentals/first-deploy.md to deploy this project, and print the Azion domain once it answers 200. `azion login` and `azion init` need an interactive terminal: when you reach them, stop and ask me to run them. For the other commands, use flags instead of prompts.</DocPrompt>

<DocSteps>
<DocStep title="Set up the Azion CLI">
Expand Down Expand Up @@ -138,7 +158,7 @@ Open the Azion domain in the browser to see your application running. If you get
The CLI builds the project, uploads it, creates the application with its domain, and prints the domain at the end.

</DocStep>
<DocStep title="Test it">
<DocStep title="Check the application">

```bash
curl -I https://<your-azion-domain>
Expand All @@ -157,7 +177,7 @@ You deployed an application to Azion's distributed infrastructure and confirmed
## Next steps

<DocCardGroup cols={3}>
<DocCard title="Go live" icon="pi pi-globe" href="/en/documentation/platform/workloads/">Add a custom domain and point your traffic to the application you just deployed.</DocCard>
<DocCard title="Use your own domain" icon="pi pi-globe" href="/en/documentation/guides/platform/migration/point-domain-to-azion/">Add a custom domain and point your traffic to the application you just deployed.</DocCard>
<DocCard title="Secure your application" icon="pi pi-shield" href="/en/documentation/platform/firewall/">Enable Firewall and WAF protection.</DocCard>
<DocCard title="Observe your application" icon="pi pi-chart-line" href="/en/documentation/platform/real-time-metrics/">Follow metrics and events in real time.</DocCard>
</DocCardGroup>
Expand Down
Original file line number Diff line number Diff line change
@@ -1,14 +1,18 @@
---
title: PCI Compliance
title: PCI compliance
description: >-
As a PCI-DSS 4.0 Level 1 Service Provider, Azion keeps your valuable data
As a PCI-DSS 4.0.1 Level 1 Service Provider, Azion keeps your valuable data
secure across all data centers, without compromising your site's
performance.
meta_tags: 'Azion, edge computing, compliance, payment card, data security and privacy'
namespace: documentation_compliance_pci
permalink: /documentation/fundamentals/pci-dss-certification/
---

import FrameBox from '@aziontech/webkit/frame-box'
import ItemList from '@aziontech/webkit/item-list'
import DocItem from '@aziontech/webkit/doc-item'

As part of the ongoing compliance efforts, Azion is always improving the internal security controls it applies to customers' data, applications, and sites running on the Azion Web Platform. This is why Azion annually renews its **PCI-DSS certification** as a **PCI DSS 4.0.1 Level 1 service provider** for the newest version released, demonstrating the commitment to ensure that the transmission and processing of cardholder data are secure for both customers and those who interact with Azion's services.

---
Expand Down Expand Up @@ -39,24 +43,36 @@ As a result, you can:

---

## Frequently asked questions
## Attestation details

- **What compliance is Azion achieving?**
### Attested level

Azion has been attested as a **PCI DSS 4.0.1 Level 1 Service Provider**.

- **Who performs the independent audit of Azion for its PCI compliance?**
### Independent auditor

Azion contracted a [Qualified Security Assessor (QSA)](https://listings.pcisecuritystandards.org/assessors_and_solutions/qualified_security_assessors). Customers on the [Enterprise plan](https://www.azion.com/en/pricing/) can request more information through a support ticket. For the support tiers that open tickets, refer to [Support guidelines](/en/documentation/support/).

- **Which regions and products are covered?**
### Products and regions covered

Azion's PCI compliance extends across the entire Azion Web Platform, which includes the Applications product and its add-ons (Application Accelerator, Cache, Functions, and Load Balancer) and the Firewall product and its add-ons (DDoS Protection, Network Shield, Web Application Firewall - WAF, and Origin Shield), covering all regions where it is deployed. Presently, Azion is deployed in six continents.
Azion's PCI compliance extends across the entire Azion Web Platform, which includes Applications, Application Accelerator, Cache, Functions, Load Balancer, Firewall, DDoS Protection, Network Shield, Web Application Firewall (WAF), and Origin Shield, covering all regions where it is deployed. Azion is deployed on six continents.

- **How long is Azion's Attestation of Compliance (AOC) valid for?**
### Attestation of Compliance validity

Azion annually renews its **PCI-DSS certification** for the newest version released. Customers on the Enterprise plan can request more details through a support ticket. For the support tiers that open tickets, refer to [Support guidelines](/en/documentation/support/).

- **How can I get a copy of Azion's Attestation of Compliance (AOC)?**
### Copy of the Attestation of Compliance

Customers on the Enterprise plan can request a copy of the Attestation of Compliance (AOC) through a support ticket. *An NDA is required*. For the support tiers that open tickets, refer to [Support guidelines](/en/documentation/support/).

---

## Related resources

Customers on the Enterprise plan can request a copy of the AOC through a support ticket. *An NDA is required*. For the support tiers that open tickets, refer to [Support guidelines](/en/documentation/support/).
<FrameBox>
<ItemList>
<DocItem title="SOC compliance" href="/en/documentation/fundamentals/soc/">Read the SOC 2 Type 2 and SOC 3 reports Azion receives.</DocItem>
<DocItem title="Shared responsibility model" href="/en/documentation/fundamentals/shared-responsibility/">See which security controls belong to Azion and which belong to you.</DocItem>
<DocItem title="Support guidelines" href="/en/documentation/support/">Open a ticket to request the Attestation of Compliance.</DocItem>
</ItemList>
</FrameBox>
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: SOC Compliance
title: SOC compliance
description: >-
Azion receives biannual SOC 2 Type 2 and SOC 3 reports, which demonstrate that
the security controls are continuously audited over the course of the year.
Expand All @@ -8,11 +8,15 @@ namespace: documentation_compliance_soc
permalink: /documentation/fundamentals/soc/
---

import FrameBox from '@aziontech/webkit/frame-box'
import ItemList from '@aziontech/webkit/item-list'
import DocItem from '@aziontech/webkit/doc-item'

Azion consistently strives to enhance internal security controls to assure customers that the applications, content, and data running on Azion Web Platform are kept safe and available. In this tradition, Azion receives biannual **SOC 2 Type 2** and **SOC 3** reports, which demonstrate that the security controls are continuously audited over the course of the year.

---

## SOC 2 Type II and SOC 3
## SOC 2 Type 2 and SOC 3

**SOC 2** is an auditing procedure developed by the **American Institute of Certified Public Accountants (AICPA)** to ensure that service providers are taking the necessary steps to maintain data security and privacy. SOC 2 attests to the trustworthiness of services provided by the organization, and it is composed of five “trust service principles” that serve as a backbone for secure data management.

Expand All @@ -24,7 +28,7 @@ Azion is evaluated on two different trust principles: **Security** and **Availab

This third-party evaluation assesses the platform's ability to prevent unauthorized access, security breaches, and security-related issues that might impact availability.

Azion's **SOC 2 Type 2** attestation applies to the entire Azion Web Platform, which includes the Applications product and its add-ons (Application Accelerator, Cache, Functions, and Load Balancer) and the Firewall product and its add-ons (DDoS Protection, Network Shield, Web Application Firewall - WAF, and Origin Shield), covering all regions where it is deployed. Azion invested effort into attesting the entire Platform for mainly one reason: performance. Flawless experiences demand that apps and data are processed and delivered as close to end users as possible, and certifying less than the entire network and Platform would lead to a performance tradeoff.
Azion's **SOC 2 Type 2** attestation applies to the entire Azion Web Platform, which includes Applications, Application Accelerator, Cache, Functions, Load Balancer, Firewall, DDoS Protection, Network Shield, Web Application Firewall (WAF), and Origin Shield, covering all regions where it is deployed. Azion invested effort into attesting the entire Platform for mainly one reason: performance. Flawless experiences demand that apps and data are processed and delivered as close to end users as possible, and certifying less than the entire network and Platform would lead to a performance tradeoff.

Additionally, Azion has gone a step further, gaining **SOC 3** attestation for customers with the most stringent regulatory and compliance needs. The SOC 3 report, attested by the same auditors who verified Azion's controls for SOC 2 Type 2, outlines information related to Azion's internal controls for security and availability, and customers on the [Enterprise plan](https://www.azion.com/en/pricing/) can request it through a support ticket.

Expand All @@ -36,20 +40,32 @@ SOC 2 Type 2 and SOC 3 designations can be used to simplify your audits and to e

---

## Frequently asked questions
## Report details

- **Who performs the independent audit of Azion for its SOC 2 Type 2 and SOC 3 reports?**
### Independent auditor

Azion's SOC 2 Type 2 and SOC 3 reports covering the Security and Availability trust service principles are generated by third-party assessors.

- **How often are the Azion SOC 2 and SOC 3 reports issued?**
### Report frequency

Azion's SOC 2 and SOC 3 reports are issued annually. Customers on the Enterprise plan can request more information through a support ticket. For the support tiers that open tickets, refer to [Support guidelines](/en/documentation/support/).

- **Which Azion products and world regions are covered?**
### Products and regions covered

Azion's SOC 2 and SOC 3 reports cover the entire web platform, which includes the Applications product and its add-ons (Application Accelerator, Cache, Functions, and Load Balancer) and the Firewall product and its add-ons (DDoS Protection, Network Shield, Web Application Firewall - WAF, and Origin Shield), in all regions where it is deployed. Presently, Azion is deployed on six continents.
Azion's SOC 2 and SOC 3 reports cover the entire web platform, which includes Applications, Application Accelerator, Cache, Functions, Load Balancer, Firewall, DDoS Protection, Network Shield, Web Application Firewall (WAF), and Origin Shield, in all regions where it is deployed. Azion is deployed on six continents.

- **Does Azion have certificates of SOC 2 and SOC 3 compliance?**
### SOC 2 and SOC 3 certificates

There is no certificate of compliance for SOC 2. Rather, qualified third-party assessors produce a report on compliance for the assessed organization, attesting to the trustworthiness of services provided by the organization. For SOC 3, customers on the Enterprise plan can request a copy of the report through a support ticket. For the support tiers that open tickets, refer to [Support guidelines](/en/documentation/support/).

---

## Related resources

<FrameBox>
<ItemList>
<DocItem title="PCI compliance" href="/en/documentation/fundamentals/pci-dss-certification/">Read about Azion's PCI DSS 4.0.1 Level 1 Service Provider attestation.</DocItem>
<DocItem title="Shared responsibility model" href="/en/documentation/fundamentals/shared-responsibility/">See which security controls belong to Azion and which belong to you.</DocItem>
<DocItem title="Support guidelines" href="/en/documentation/support/">Open a ticket to request the SOC 3 report.</DocItem>
</ItemList>
</FrameBox>
Loading
Loading