ARXIMUS CLOUD

PAY AS YOU GO
AI Runtime Authorization Priced by Usage

Route AI interactions and agent activity through Arximus Cloud. Runtime authorization and security controls are metered at $1 per 1 million secured tokens, with no flat request fee.

Request access Explore platform

ARXIMUS CLOUD USAGE PRICING

$ 1.00

per 1M secured tokens

INPUT TOKENS METERED

OUTPUT TOKENS METERED

FLAT REQUEST FEE NONE

BILLING PAY AS YOU GO

Input and output tokens combine into one secured-token total. You pay only for the token volume Arximus processes.

MANAGED CLOUD $1 / 1M PAY AS YOU GO NO REQUEST FEE RUNTIME AUTHORIZATION PROVIDER NEUTRAL

ARXIMUS CLOUD BILLING

Secured token volume determines cost.

Each request is metered by the input and output tokens Arximus processes. They combine into one secured-token total billed at $1 per 1 million, with no flat request fee.

01 / REQUEST

Traffic enters Arximus

An application, agent or AI system sends traffic through the Arximus Cloud security path.

02 / INPUT

Input becomes secured usage

Input tokens processed through runtime authorization, inspection and security controls contribute to secured-token usage.

03 / OUTPUT

Output becomes secured usage

Output tokens processed by Arximus, including model responses, tool calls and agent action payloads, contribute to the same usage total.

04 / COST

One total determines cost

Input and output are combined and billed at one rate of $1 for every 1 million secured tokens processed.

EXAMPLE SECURED REQUEST

INPUT 8,000 secured tokens

OUTPUT 2,000 secured tokens

TOTAL 10,000 secured tokens

ARXIMUS COST $0.01 at $1 / 1M

BILLING RULES

One rate across secured AI traffic.

Input and output use the same $1 per 1 million secured-token rate. There is no flat request fee, and billing follows the token volume Arximus processes.

INPUT

Input and context

Prompts, context, retrieved content and other request data processed by Arximus count toward secured input-token usage.

OUTPUT

Responses and actions

Model responses, tool calls, action payloads and other output content processed by Arximus count toward secured output-token usage at the same rate.

REQUESTS

No flat request fee

Request count does not create a separate charge. Usage cost follows the secured-token volume Arximus processes.

ENFORCEMENT

Processed traffic is metered

Metering follows processing rather than enforcement outcome. Allowed, denied, restricted or otherwise controlled traffic uses the same secured-token rate.

PROVIDERS

One meter across providers

The Arximus meter applies independently of the underlying AI provider, including provider-hosted, private and self-hosted systems routed through Arximus.

BILLING

Pay as you go

Pay according to the secured-token volume Arximus processes, under the billing terms applicable to your Arximus Cloud service.

PRICING DETAILS

How Cloud usage is measured.

Arximus Cloud usage is billed independently of model-provider and infrastructure charges. The secured-token meter determines the Arximus usage cost.

What is a secured token?

A secured token is a billing unit produced by the Arximus metering standard from the input and output content Arximus processes, including prompts, context, responses, tool calls and action payloads. Input and output are combined to determine total secured-token usage.

How are secured tokens measured?

Arximus uses a fixed, versioned and provider-neutral metering standard rather than token counts reported by the underlying AI provider. Supported structured payloads are normalized before measurement so insignificant formatting differences do not change usage. The same metering standard applies across provider-hosted, private and self-hosted AI.

Does Arximus retain my AI traffic?

AI content is not retained by default after runtime processing. Customers can enable content logging and define retention where needed. Structured security evidence is preserved separately from optional content logs, while policy can capture selected, redacted or complete content for blocked and high-risk events when deeper forensic review is required.

Are input and output priced differently?

No. Both are billed at the same rate of $1 per 1 million secured tokens.

Do requests have a separate charge?

No. Arximus tracks requests for security and operational visibility, but the usage charge is determined by secured token volume.

What happens when Arximus blocks a request or action?

Arximus meters the tokens it processes regardless of whether the content is allowed or blocked. If output such as a model response, tool call or action payload reaches Arximus, those output tokens are metered even when Arximus prevents the output or action from proceeding. Metering is based on processing, not retention. Blocked and high-risk events produce structured security evidence, while policy can additionally capture selected, redacted or complete content for forensic review.

Can this work with private or self-hosted AI?

Yes. Arximus can secure traffic to private and self-hosted AI systems. Arximus Enterprise can also provide dedicated Arximus-operated infrastructure, private connectivity and contracted regional requirements for organizations with stricter security and network boundaries.

Are model-provider charges included?

No. OpenAI, Anthropic, Google, cloud infrastructure or private-model costs remain separate from Arximus Cloud usage.

What is the difference between Arximus Cloud and Arximus Enterprise?

Arximus Cloud provides the standard Arximus-managed deployment and usage model. Arximus Enterprise uses custom annual commitments and contracted usage for organizations that require dedicated environment options, private connectivity, regional and data controls, enterprise governance, Arximus Lock deployment or additional contractual service requirements.