Get the security and controls you need. No credit card required.
AxisNow's workloads refer to the applications or services that you run for your clients or employees, as well as the client software entities that you publicly distribute. Examples include custom applications, daemons, ETL processors, one-time or batch jobs, and deployment scripts or containers. Typically, they run in the background and must access resources on behalf of themselves using their own workload identity, without any user intervention.The workload identity is an identity assigned to a workload, used for authentication and access to resources. This term is not consistent throughout the industry, but typically, a workload entity requires a workload identity to be authenticated through certain systems.
AxisNow each endpoint quota can be used for Client Endpoint or Service Endpoint.Client Endpoint: Each workload counts as 1 endpoint. Service Endpoint: Each resource counts as 1 endpoint.
In AxisNow, the client endpoint consists of two key components: the workload(application) and the device(runtime environment).Workload: This refers to any computational tasks or processes that you deploy or manage. Examples include publicly distributed client software, custom applications you develop and run, scripts, and containers. Each workload entity is uniquely identified by a set of conditions defined within AxisNow.Device: This encompasses any computing environment where the workload operates. Examples include devices such as desktop computers, smartphones, tablets, laptops, and Internet of Things (IoT) devices, as well as infrastructure components like servers, virtual machines and containers.
In AxisNow, Service endpoint are resource provided for requests from client endpoints. Examples include web APIs, third-party SaaS APIs, API gateways, databases, and data warehouses.
We currently do not limit the number of administrators who can add to AxisNow, regardless of how many available licenses you have.
AxisNow defines the absence of your integrated identity or endpoint data in the HTTP/HTTPS request context as Regular HTTP requests(RHR). One HTTPS request counts as 5 RHRs. Typical use cases include WAAP, API gateway, Reverse Proxy, CDN, and Load Balancing.
We currently do not limit the number of administrators who can add to AxisNow. Instead, we operate on a monthly mid-term adjustment process. Once a month, the AxisNow team will review your active count to assess current usage. If we find that your active count exceeds your allocated license number, we will send you an email 5 days before charging your account to notify you of the excess charges.
Yes. For our enterprise version, we offer bulk discounts for annual payments over $50,000. Please contact our sales team for more details.
We place great importance on data security. We strive to protect tenant data as much as possible. At the same time, AxisNow supports you to log out of the tenant at any time and delete all data.AxisNow's infrastructure (including Proxy and Agent) is installed and managed directly in your own cloud infrastructure. This approach ensures that all data is managed and stored locally, allowing you to have complete control over the data without external influences.In contrast, AxisNow's control plane is a SaaS (Software as a Service) product that provides centralized control over all AxisNow components. The data displayed in the UI includes aggregated metrics of system telemetry, system usage, and endpoint access. Importantly, customers can disable this data sharing feature of the SaaS product, thereby flexibly controlling the amount of information transmitted and reflected in the UI.