Skip to content
Gauge

ax-check.com

by Gauge

Omnistrate

omnistrate.com

ax-check.com

Checked 19 September 2026

B

69/100

Agents need your login

Docs and CLI setup are solid, but pricing page has no prices.

Quickstarts, API docs, and MCP setup all check out, but the pricing page itself shows no plans, costs, or usage limits.

5 fixes to start with

Concrete changes, backed by what we found.

Onboarding

Give agents a clear login handoff and a way to resume setup.

Agents cannot progress through onboarding without human help. Provide an agent-accessible path through authentication and setup.

Docs

Publish a public pricing page that agents can read without interaction.

Pricing page fetched but contains no plan or price content, only nav and footer.

Docs

Publish prices alongside the sales contact.

No prices are stated anywhere on the fetched pricing page.

Docs

State what each price includes and how overages are billed.

No pricing units, seats, usage limits or billing dimensions are described.

Docs

Return Markdown when clients request text/markdown.

Homepage returned text/html for a text/markdown request; no Markdown representation offered.

Recorded coding sessions

Same task, 3 models, no omnistrate.com account. Recorded 19 September 2026 on Pi.

3 recorded · 5m 8s

5m 8s · recorded

Session findings

Select a finding to see it in context.

piv0.84.2
modelQwen 3.8 Maxcwd/sandbox/repo
Help me build a simple example using Omnistrate. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop.
Thinking…

The user is asking about "Omnistrate" — a product for building SaaS. First, let me check the repository to see what's there. Also, there might be MCP tools, but I only have read/bash/edit/write.

First, let me check the working directory.

$ pwd; ls -la; ls -la /sandbox 2>/dev/null{"content":[{"text":"/sandbox/repo\ntotal 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 19 04:26 ..\ndrwxr-xr-x 8 root root 40…ctrl+o
{"content":[{"text":"/sandbox/repo\ntotal 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 19 04:26 ..\ndrwxr-xr-x 8 root root 4096 Sep 18 08:00 .git\n-rw-r--r-- 1 root root  408 Sep 18 08:00 .gitignore\ntotal 28\ndrwxr-xr-x  7 root root 4096 Sep 19 04:26 .\ndrwxr-xr-x 22 root root 4096 Sep 18 07:59 ..\ndrwxr-xr-x  3 root root 4096 Sep 19 04:26 .cache\ndrwxr-xr-x  3 root root 4096 Sep 19 04:26 .gauge\ndrwxr-xr-x  3 root root 4096 Sep 19 04:26 .pi\ndrwxrwxrwt  2 root root 4096 Sep 18 08:00 .tmp\ndrwxr-xr-x  3 root root 4096 Sep 18 08:00 repo\n","type":"text"}]}
$ env | grep -i -E "omnistrate|PI_" | head -50{"content":[{"text":"PI_CODING_AGENT=true\nPI_REASONING_LEVEL=medium\nPI_SESSION_FILE=/sandbox/.gauge/pi/sessions/2026-09-19T04-26-43-216Z_01a0b7ea-a490-7f1f-b4…ctrl+o
{"content":[{"text":"PI_CODING_AGENT=true\nPI_REASONING_LEVEL=medium\nPI_SESSION_FILE=/sandbox/.gauge/pi/sessions/2026-09-19T04-26-43-216Z_01a0b7ea-a490-7f1f-b4fb-9bc7ad986e6c.jsonl\nPI_PROVIDER=gauge-fireworks\nPI_MODEL=accounts/fireworks/models/qwen3p8-max\nPI_SESSION_ID=01a0b7ea-a490-7f1f-b4fb-9bc7ad986e6c\nPI_GATEWAY_API_KEY=unused\n","type":"text"}]}
Thinking…

The repo is empty. The user wants to build a simple example using Omnistrate — a hosted product with an SDK/API. Omnistrate is a platform for building SaaS products (Omnistrate's FaaS/omnistrate-cli). There are Python and TypeScript SDKs: omnistrate-sdk on npm, omnistrate-client on PyPI? Trying to recall: Omnistrate provides generated SDKs (omnistrate-api). The API requires an account/API key (email + password auth, or token). Building a simple example requires an Omnistrate account, which I don't have. Also, network access may be restricted.

Let me check network access and whether credentials are available. If no credentials, I'll report that it's blocked — the hosted product requires an account, and while I can write example code using the SDK, I can't run it. The instructions say: "If this product doesn't have a developer workflow you can act on, say so plainly and stop." Omnistrate does have a developer workflow (CLI + Terraform + SDK), but it requires an account and provisioning on cloud infrastructure (deploying services to AWS/GCP), which is a long-running operation and also requires credentials.

Let me quickly check: do we have internet? Do we have an Omnistrate API key?

$ env | grep -i -E "key|token|secret|pass" | head -30; echo ---; curl -s -m 8 -o /dev/null -w "%{http_code}\n" https://api.omnistrate.com/ 2>&1; echo ---; curl -s -m 8 -o /dev/null -w "%{http_code}\n" h…{"content":[{"text":"PI_GATEWAY_API_KEY=unused\nGIT_CONFIG_KEY_0=safe.directory\n---\n000\n---\n404\n","type":"text"}]}ctrl+o
env | grep -i -E "key|token|secret|pass" | head -30; echo ---; curl -s -m 8 -o /dev/null -w "%{http_code}\n" https://api.omnistrate.com/ 2>&1; echo ---; curl -s -m 8 -o /dev/null -w "%{http_code}\n" https://registry.npmjs.org/omnistrate-sdk 2>&1
Thinking…

Interesting point: api.omnistrate.com returned 000 (connection failed?), while npmjs returned 404 (meaning the network is working, but the package name might be wrong). Let me check the network more. npm registry is reachable (a 404 means the package "omnistrate-sdk" doesn't exist under that name?). Let me search the npm registry and pypi.

$ curl -s -m 10 "https://registry.npmjs.org/-/v1/search?text=omnistrate&size=10" | python3 -c "import json,sys; d=json.load(sys.stdin); [print(o['package']['name'], o['package'].get('version'), o['packa…{"content":[{"text":"(no output)","type":"text"}]}ctrl+o
curl -s -m 10 "https://registry.npmjs.org/-/v1/search?text=omnistrate&size=10" | python3 -c "import json,sys; d=json.load(sys.stdin); [print(o['package']['name'], o['package'].get('version'), o['package'].get('description','')[:80]) for o in d['objects']]" 2>&1 | head
$ curl -s -m 10 "https://pypi.org/pypi/omnistrate-client/json" -o /dev/null -w "%{http_code}\n"; curl -s -m 10 "https://pypi.org/pypi/omnistrate/json" -o /dev/null -w "%{http_code}\n"; curl -s -m 10 htt…{"content":[{"text":"404\n404\n* Could not resolve host: api.omnistrate.com\n* Closing connection\n","type":"text"}]}ctrl+o
curl -s -m 10 "https://pypi.org/pypi/omnistrate-client/json" -o /dev/null -w "%{http_code}\n"; curl -s -m 10 "https://pypi.org/pypi/omnistrate/json" -o /dev/null -w "%{http_code}\n"; curl -s -m 10 https://api.omnistrate.com -v 2>&1 | tail -5
Thinking…

Did the npm search return empty? Let me check the raw output. Also, api.omnistrate.com can't be resolved by name. Let me check what the actual Omnistrate API domain is. Probably something like "api.omnistrate.com" or "console.omnistrate.com". DNS is failing—this sandbox might have restricted DNS, or that host might not actually exist. Let me check pypi search and npm raw.

$ curl -s -m 10 "https://registry.npmjs.org/-/v1/search?text=omnistrate&size=5" | head -c 500; echo; echo ---; curl -s -m 10 "https://pypi.org/simple/" -o /dev/null -w "pypi:%{http_code}\n"; nslookup om…{"content":[{"text":"{\"objects\":[],\"total\":0,\"time\":\"2026-09-19T04:26:57.139Z\"}\n---\npypi:200\nAddress: 2606:4700:3036::6815:3e44\nName:\tomnistrate.co…ctrl+o
curl -s -m 10 "https://registry.npmjs.org/-/v1/search?text=omnistrate&size=5" | head -c 500; echo; echo ---; curl -s -m 10 "https://pypi.org/simple/" -o /dev/null -w "pypi:%{http_code}\n"; nslookup omnistrate.com 2>&1 | tail -4; nslookup api.omnistrate.cloud 2>&1 | tail -4

{"content":[{"text":"{\"objects\":[],\"total\":0,\"time\":\"2026-09-19T04:26:57.139Z\"}\n---\npypi:200\nAddress: 2606:4700:3036::6815:3e44\nName:\tomnistrate.com\nAddress: 2606:4700:3036::ac43:dd0e\n\nAddress: 16.144.192.51\nName:\taf96c177bf28a498483f6a1ec95e53fc-2113758822.us-west-2.elb.amazonaws.com\nAddress: 54.212.168.156\n\n","type":"text"}]}
Thinking…

I see, api.omnistrate.cloud can be resolved (this is Omnistrate's actual API host). The npm search didn't return anything for "omnistrate" — weird, but maybe the search index is being restricted. Let me directly check the actual package names on the npm registry: "omnistrate-cli"? Omnistrate's tools: omnistrate-cli (Go binary, brew), generated SDKs: e.g. "omnistrate-sdk-typescript"? Actually, Omnistrate generates customer-facing SDKs (OmnistrateSDK) per service. The platform's OpenAPI client is generated by the user from the openapi spec. There are GitHub repos too: omnistrate/omnistrate-ctl, omnistrate-signup? Let me check the npm registry directly.

$ for p in omnistrate omnistrate-api omnistrate-client @omnistrate/sdk omnistrate-openapi; do printf "%s: " "$p"; curl -s -m 8 -o /dev/null -w "%{http_code}\n" "https://registry.npmjs.org/$(python3 -c "…{"content":[{"text":"omnistrate: 404\nomnistrate-api: 404\nomnistrate-client: 404\n@omnistrate/sdk: 404\nomnistrate-openapi: 404\n","type":"text"}]}ctrl+o
for p in omnistrate omnistrate-api omnistrate-client @omnistrate/sdk omnistrate-openapi; do printf "%s: " "$p"; curl -s -m 8 -o /dev/null -w "%{http_code}\n" "https://registry.npmjs.org/$(python3 -c "import urllib.parse,sys;print(urllib.parse.quote(sys.argv[1],safe=''))" "$p")"; done
$ curl -s -m 10 -o /dev/null -w "api.omnistrate.cloud: %{http_code}\n" https://api.omnistrate.cloud/; curl -s -m 10 "https://api.omnistrate.cloud/" | head -c 300; echo{"content":[{"text":"api.omnistrate.cloud: 404\n<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr>…ctrl+o
{"content":[{"text":"api.omnistrate.cloud: 404\n<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n\n","type":"text"}]}
Thinking…

So api.omnistrate.cloud exists and is reachable (nginx 404 at the root, which is normal). The official Omnistrate SDK doesn't exist on npm — the workflow is: sign up for an Omnistrate account (web console), use omnistrate-cli or the Web UI to create service plans (via Terraform-based compose files), and then the platform generates customer-facing OpenAPI/SDKs for your own SaaS. The "platform API" is documented at docs.omnistrate.com, and API access requires account credentials (JWT auth via login with email/password).

Key questions for this task:

  1. Are credentials available? No — no environment variables.
  2. Can you sign up via the API without a human? Omnistrate's signup probably requires web/Google OAuth, or an email verification code. Trying to create an account on a third-party hosted service without the user's consent or credentials is problematic.

The actual developer workflow for Omnistrate (CLI, Terraform service definitions, SDK generation, deployment to your own AWS/GCP account) does exist. However:

  • It requires an Omnistrate account (credentials not provided).
  • It requires cloud provider (AWS/GCP) credentials to deploy services.
  • Service deployment is long-running.

The instructions say: "Stay lightweight: use hosted products via their SDK or API. Do not launch local service stacks or execute long-running commands. If the quickstart requires either, state so frankly and stop."

The Omnistrate quickstart requires: account signup, installing omnistrate-cli, configuring cloud accounts (AWS/GCP), and deploying a service — this provisions real infrastructure and takes time (several minutes or more). This is effectively long-running and requires credentials that aren't available.

Therefore the correct action is: report frankly. But also answer the pricing question and the "is it easy to manage" question.

Should I still write a sample file? The instructions say: "If this product doesn't have an actionable developer workflow, state so frankly and stop." Omnistrate does have a developer workflow, but it's not one I can act on here (no credentials, needs cloud account, long-running deployment). The quickstart requires long-running commands (service deployment) and external credentials → per instructions, state so frankly and stop.

Quickly confirm that the signup API requires interactive/email verification, and check the pricing docs to answer accurately. Try fetching the pricing page from docs.omnistrate.com.

$ curl -s -m 10 -L "https://omnistrate.com/pricing/" | python3 -c "{"content":[{"text":" Pricing Plans | Omnistrate Developer Pricing About Sign in Start for Free The AI infrastructure standard built for secure, enterprise-grad…ctrl+o
curl -s -m 10 -L "https://omnistrate.com/pricing/" | python3 -c "
import sys,re,html
t=sys.stdin.read()
t=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
print(t[:3000])"

{"content":[{"text":" Pricing Plans | Omnistrate Developer Pricing About Sign in Start for Free The AI infrastructure standard built for secure, enterprise-grade software distribution. Company About us Contact us Careers Terms of Service Privacy Policy Trust Center Cookie Settings Product Sign in Sign up Pricing Support Demo Resources Documentation Engineering Blog Why Omnistrate? Omnistrate, Demystified API Reference Customer Stories Ecosystem Events Community Partners Press Release AWS SaaS Offer © 2026 Omnistrate, Inc. All rights reserved. Terms Privacy Cookie Policy Status \n","type":"text"}]}
$ curl -s -m 10 "https://api.omnistrate.cloud/openapi.json" -o /dev/null -w "%{http_code}\n"; curl -s -m 10 -L "https://docs.omnistrate.com/" | python3 -c "{"content":[{"text":"404\n Omnistrate Documentation Skip to content Omnistrate Documentation Introduction Initializing search Omnistrate Documentation Introduct…ctrl+o
curl -s -m 10 "https://api.omnistrate.cloud/openapi.json" -o /dev/null -w "%{http_code}\n"; curl -s -m 10 -L "https://docs.omnistrate.com/" | python3 -c "
import sys,re,html
t=sys.stdin.read()
t=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
print(t[:2000])"

{"content":[{"text":"404\n Omnistrate Documentation Skip to content Omnistrate Documentation Introduction Initializing search Omnistrate Documentation Introduction Introduction Table of contents Introduction to Omnistrate How Omnistrate Transforms Your Product Distribution Common Distribution Challenges We Solve Explore by Your Role For Platform Developers For Product & Business Teams For DevOps & SRE Teams For FinOps & Business Operations For SecOps & Governance Why Choose Omnistrate? Distribution Channels Take Years to Build and an Army to Operate—Not Anymore Get Started in Minutes, Not Months Connect with us What is Omnistrate What you can do Cost vs. Benefits Architecture Getting Started Getting Started Overview Account Onboarding Account Onboarding Overview Cloud account guides for CTL AWS account onboarding with CTL GCP account onboarding with CTL Azure account onboarding with CTL Nebius Nebius Account onboarding with CTL Example: Deploy vLLM on Nebius Installing CLI AI Agent Setup From Source Repo From Compose From Helm charts From Operators From Kustomize From Terraform Quick start with CLI Quick start with UI Zero to SaaS Product Build Guide Build Guide Overview Plan Deployment models Tenancy types Resource Resource Visibility Resource Dependencies Resource Linking Deployment API Params System Parameters Expression Evaluator Action Hooks Deployment Cells Integrations Specification Reference Specification Reference Specification Choice Compose Specification Overview Plan Specification Build by Deployment Strategy Build by Deployment Strategy Compose Compose Overview Compose Specification Troubleshooting Helm Helm Overview Helm Chart Customization Helm Chart Topology Layered Chart Values Runtime Configuration Helm and Terraform Troubleshooting Kubernetes Operators Kubernetes Operators Overview Kubernetes Operators Troubleshooting Terraform Terraform Overview Multi-Cloud Configuration Input Parameters and Output Mapping Troubleshooting Build by Use Case Build by Use Case Cellular Multi\n","type":"text"}]}
Thinking…

The content of the pricing page is mostly navigation. Let's try to grab more of the pricing content (it might be rendered by JS). I'll try fetching the raw pricing page and searching for "$" or "plan".

$ curl -s -m 10 -L "https://omnistrate.com/pricing/" | python3 -c "{"content":[{"text":"\n","type":"text"}]}ctrl+o
curl -s -m 10 -L "https://omnistrate.com/pricing/" | python3 -c "
import sys,re,html
t=sys.stdin.read()
t=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
import textwrap
print(t[1000:5000])"
Thinking…

The content of the pricing page might be rendered by JS (or it could be that only navigation is loaded via server-side rendering, and the actual pricing cards are rendered client-side). Let me try fetching the raw HTML and grepping for keywords like "$", "free", "enterprise", "platform fee", "per", etc.

$ curl -s -m 10 -L "https://omnistrate.com/pricing/" -o /tmp/pricing.html; wc -c /tmp/pricing.html; grep -o -i -E "(\$\s?[0-9,.]+[a-z/ ]{0,20}|free trial|platform fee|per (month|environment|service)|usa…{"content":[{"text":"40040 /tmp/pricing.html\n 1 enterprise\n","type":"text"}]}ctrl+o
curl -s -m 10 -L "https://omnistrate.com/pricing/" -o /tmp/pricing.html; wc -c /tmp/pricing.html; grep -o -i -E "(\$\s?[0-9,.]+[a-z/ ]{0,20}|free trial|platform fee|per (month|environment|service)|usage-based|developer plan|enterprise|startup|business plan)" /tmp/pricing.html | sort | uniq -c | sort -rn | head -30
Thinking…

The pricing page is JS-rendered, and the static HTML doesn't contain the pricing details. Let me check the pricing info in the documentation. For example, the "Cost vs. Benefits" page on docs.omnistrate.com, or searching within the docs, etc. I'll fetch https://docs.omnistrate.com/ and look for pricing/cost pages.

$ grep -o -E 'href="[^"]*"' /tmp/pricing.html | sort -u | grep -i -E "json|next|data|price" | head; echo ---; curl -s -m 10 -L "https://docs.omnistrate.com/what-is-omnistrate/cost-vs-benefits/" | python…{"content":[{"text":"href=\"/_next/static/chunks/0oj818unuuvj2.js\"\nhref=\"/_next/static/chunks/2imjndafru3oz.css\"\n---\n Omnistrate Documentation Omnistrate …ctrl+o
grep -o -E 'href="[^"]*"' /tmp/pricing.html | sort -u | grep -i -E "json|next|data|price" | head; echo ---; curl -s -m 10 -L "https://docs.omnistrate.com/what-is-omnistrate/cost-vs-benefits/" | python3 -c "
import sys,re,html
t=sys.stdin.read()
t=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
print(t[:3500])"

{"content":[{"text":"href=\"/_next/static/chunks/0oj818unuuvj2.js\"\nhref=\"/_next/static/chunks/2imjndafru3oz.css\"\n---\n Omnistrate Documentation Omnistrate Documentation Initializing search Omnistrate Documentation Introduction What is Omnistrate What you can do Cost vs. Benefits Architecture Getting Started Getting Started Overview Account Onboarding Account Onboarding Overview Cloud account guides for CTL AWS account onboarding with CTL GCP account onboarding with CTL Azure account onboarding with CTL Nebius Nebius Account onboarding with CTL Example: Deploy vLLM on Nebius Installing CLI AI Agent Setup From Source Repo From Compose From Helm charts From Operators From Kustomize From Terraform Quick start with CLI Quick start with UI Zero to SaaS Product Build Guide Build Guide Overview Plan Deployment models Tenancy types Resource Resource Visibility Resource Dependencies Resource Linking Deployment API Params System Parameters Expression Evaluator Action Hooks Deployment Cells Integrations Specification Reference Specification Reference Specification Choice Compose Specification Overview Plan Specification Build by Deployment Strategy Build by Deployment Strategy Compose Compose Overview Compose Specification Troubleshooting Helm Helm Overview Helm Chart Customization Helm Chart Topology Layered Chart Values Runtime Configuration Helm and Terraform Troubleshooting Kubernetes Operators Kubernetes Operators Overview Kubernetes Operators Troubleshooting Terraform Terraform Overview Multi-Cloud Configuration Input Parameters and Output Mapping Troubleshooting Build by Use Case Build by Use Case Cellular Multi-Tenancy Cellular Multi-Tenancy Overview Deployment Guide Dedicated Tenancy Dedicated Tenancy Overview Deployment Guide BYOC Anywhere BYOC Anywhere Overview BYOC Deployment Air-Gapped Air-Gapped Overview Air-Gapped Deployment App Runtime Guide App Runtime Guide Overview Autoscaling Serverless Custom Autoscaling Backups Custom Sidecars Customer Networks Licensing Protection Custom Tagging Cloud Provider Quotas Infrastructure Guide Infrastructure Guide Overview Endpoint Aliases Persistent Volumes Shared File System Blob storage Storage for Helm Charts Local NVMe Storage Deployment Cell Placement Compute Management GPU Accelerator GPU Slicing Tenancy Guide Tenancy Guide Overview User Management Subscription Management Customer Portal Identity Providers (SSO) Build Your Own Portal Private Networking DevOps Guide DevOps Guide Overview Environments Pipelines Upgrades Secrets Operations Guide Operations Guide Overview Fleet Dashboard Manage Deployments Manage Snapshots Manage Workflows Instance Breakpoints Troubleshooting Remotely Access Cells Adopt Deployment Cells Deployment Cell Amenities Managed Workload Identities Deployment Cell Node Pools Adopt Deployment BYOC Cloud Accounts AWS CloudFormation Account Controls Monitoring Alarms Webhook Payloads Governance Guide Governance Guide Security Overview Omnistrate RBAC API Keys Cloud Permissions Audit Logs FinOps Guide FinOps Guide Overview End-to-End Billing Metering Custom Usage Metering Marketplace Marketplace Fulfillment Marketplace Fulfillment Overview Connecting Suger The Sandbox Channel Simulation Controls Contract Flow API Guide Cost Insights Use cases Use cases Overview Case Studies SaaS PaaS Agent-aaS Bring Your Own Cloud BYOC PrivateLink BYOC On-Premise Air-Gapped Internal SaaS/PaaS OpenSource SaaS/PaaS Operator-powered SaaS Extend your Platform Examples API resources Command line Glossary FAQ References 404 - Not found Back to top Copyright © 2026 Omnistrate, Inc. All rights reserved. Made with M\n","type":"text"}]}
Thinking…

The Cost vs. Benefits page didn't actually display any content (nav only). I'll try searching for the pricing details. Omnistrate's pricing model (based on general knowledge): Omnistrate charges platform fees based on the deployment model — free developer tier/trial, paid plans (Developer, Startup/Business, Enterprise), priced per managed environment/deployment unit, with no fees collected on customers' infrastructure (you pay your own cloud costs); BYOC means the customer's cloud account bears the infrastructure costs, and Omnistrate charges the platform fee. I'll try fetching a few pricing-related documentation pages, or search the Next.js chunks. Actually, I'll try fetching the pricing data from the Next.js build manifest, or alternatively check web archives or blog posts about pricing.

Quick approach: grep for "self-hosted" pricing on their site, or fetch https://omnistrate.com/pricing with JS? Can't render JS. I'll try r.jina.ai? External proxies may not be allowed, but DNS works for many hosts. I'll try https://r.jina.ai/https://omnistrate.com/pricing/.

$ curl -s -m 20 "https://r.jina.ai/https://omnistrate.com/pricing/" | head -c 3500{"content":[{"text":"Title: Omnistrate Pricing Plans - Flexible SaaS Pricing for Every Need\n\nURL Source: https://omnistrate.com/pricing/\n\nMarkdown Content:\…ctrl+o
{"content":[{"text":"Title: Omnistrate Pricing Plans - Flexible SaaS Pricing for Every Need\n\nURL Source: https://omnistrate.com/pricing/\n\nMarkdown Content:\n[![Image 1](https://omnistrate.com/assets/images/logo.svg)](https://omnistrate.com/)\n*   Developer\n[* Pricing](https://omnistrate.com/pricing)[* About](https://omnistrate.com/about)\n\n[Sign in](https://omnistrate.cloud/signin)[Start for Free](https://omnistrate.cloud/signup)\n\n## Unlock New Distribution Channels and Grow Faster\n\nBuild distribution in days — not years. Pay only for outcomes.\n\n[Start your 1 month free trial No credit card required](https://omnistrate.cloud/signup)\n\nStarter\n\nFor ISVs delivering managed software across customer clouds and on-premises, with ISV-managed or customer-managed infrastructure.\n\n$100 per [active deployment](https://omnistrate.com/pricing/#active-deployments) per month\n\n[Get started](https://omnistrate.cloud/signup)\n\nWhat's included\n\nYour control plane runs in your account. Omnistrate is never in the customer data path.\n\nDeploy to customer environments across clouds and on-premises\n\nISV-managed or customer-managed infrastructure\n\nPrivate-label customer portal on your domain\n\nFleet-wide intelligent upgrades\n\nVersion management, environments, and release pipelines\n\nLogs, metrics, dashboards, and observability integrations\n\nMonitoring with automated recovery and real-time notifications\n\nEnterprise SSO / IdP integration, RBAC, API keys, secrets management, immutable audit logs, authenticated endpoints, and encryption in transit\n\nManaged private registry support\n\nSubscription and license management\n\nAWS Marketplace listing with fulfillment integration\n\nAir-gapped environment support\n\n[Basic support](https://omnistrate.com/terms/sla)\n\nOptional add-on: [Standard support](https://omnistrate.com/terms/sla)$999/month minimum commit\n\nWhite-glove onboarding\n\nWhite-glove marketplace listing\n\nGuaranteed response times\n\nGrowth\n\nFor growing ISVs delivering fully managed services across their cloud and customer clouds—with monetization and day-2 automation.\n\nvCPU-hour based pricing\n\nPer-deployment pricing also available\n\n[Contact us](https://omnistrate.com/contact)\n\nWhat's included\n\nEverything in Starter\n\nNative BYOC and BYO-VPC across clouds\n\nHosted SaaS across dedicated, multi-tenant and custom tenancy models\n\nOmnistrate-managed infra management - write once, works anywhere\n\nFleet-wide observability and insights\n\nDay-2 lifecycle controls: scale, backup, restore, failover, drift detection, start/stop, and more\n\nCustomer-controlled governance, PrivateLink, least-privilege cloud access, egress allowlisting, encryption at rest, and customer-managed networks\n\nUsage metering including custom metrics, billing, invoicing, and Stripe payments\n\nCost insights and controls\n\nAWS Marketplace billing integration\n\n[Priority support](https://omnistrate.com/terms/sla)\n\nEnterprise\n\nFor organizations requiring enterprise SLAs, dedicated support, custom integrations, and compliance.\n\nCustom pricing\n\n[Contact us](https://omnistrate.com/contact)\n\nWhat's included\n\nEverything in Growth\n\nCustom day-2 workflows\n\nCustom integrations\n\nCustom-network management\n\nOn-demand connections, customer-managed private registry support, and advanced security controls\n\nEnterprise security review assistance\n\nCompliance and pentest reports\n\nMulti-cloud marketplace listing\n\nMulti-cloud marketplace channels and integration\n\nEnterprise SLA\n\n[Enterprise support](https://omnistrate.com/terms/sla)\n\n[Contact us](https://omnistra","type":"text"}]}
Thinking…

With this, I've obtained the pricing info. To understand the pricing unit, let me also grab the definition of "Active Deployment" that appears further down the page.

$ curl -s -m 20 "https://r.jina.ai/https://omnistrate.com/pricing/" | sed -n '/active deployment/I,$p' | head -60; echo ===; curl -s -m 20 "https://r.jina.ai/https://omnistrate.com/pricing/" | grep -n -…{"content":[{"text":"$100 per [active deployment](https://omnistrate.com/pricing/#active-deployments) per month\n\n[Get started](https://omnistrate.cloud/signup…ctrl+o
curl -s -m 20 "https://r.jina.ai/https://omnistrate.com/pricing/" | sed -n '/active deployment/I,$p' | head -60; echo ===; curl -s -m 20 "https://r.jina.ai/https://omnistrate.com/pricing/" | grep -n -i -A6 "what is an active|active deployments are|FAQ" | head -40

{"content":[{"text":"$100 per [active deployment](https://omnistrate.com/pricing/#active-deployments) per month\n\n[Get started](https://omnistrate.cloud/signup)\n\nWhat's included\n\nYour control plane runs in your account. Omnistrate is never in the customer data path.\n\nDeploy to customer environments across clouds and on-premises\n\nISV-managed or customer-managed infrastructure\n\nPrivate-label customer portal on your domain\n\nFleet-wide intelligent upgrades\n\nVersion management, environments, and release pipelines\n\nLogs, metrics, dashboards, and observability integrations\n\nMonitoring with automated recovery and real-time notifications\n\nEnterprise SSO / IdP integration, RBAC, API keys, secrets management, immutable audit logs, authenticated endpoints, and encryption in transit\n\nManaged private registry support\n\nSubscription and license management\n\nAWS Marketplace listing with fulfillment integration\n\nAir-gapped environment support\n\n[Basic support](https://omnistrate.com/terms/sla)\n\nOptional add-on: [Standard support](https://omnistrate.com/terms/sla)$999/month minimum commit\n\nWhite-glove onboarding\n\nWhite-glove marketplace listing\n\nGuaranteed response times\n\nGrowth\n\nFor growing ISVs delivering fully managed services across their cloud and customer clouds—with monetization and day-2 automation.\n\nvCPU-hour based pricing\n\nPer-deployment pricing also available\n\n[Contact us](https://omnistrate.com/contact)\n\nWhat's included\n\nEverything in Starter\n\nNative BYOC and BYO-VPC across clouds\n\nHosted SaaS across dedicated, multi-tenant and custom tenancy models\n\n===\n","type":"text"}]}
Thinking…

Grab the pricing information. Next, assess feasibility. Omnistrate's developer workflow:

  1. Sign up for an account at omnistrate.cloud (free trial, no credit card required) — signup is probably possible via API? Signup requires an email verification code, and there's also a possibility that phone/Google OAuth is needed. Even if I could create an account, creating an account on a third-party hosted service without user instruction is... no wait, the user is actually requesting "help me build a simple example using Omnistrate," and says "use the hosted product via SDK or API." So signup might be in scope. However, the Omnistrate CLI/API quickstart further requires:
    • Onboarding a cloud account (AWS/GCP) — actual AWS/GCP credentials are needed in order to deploy services.
    • Service deployment — long-running (infrastructure provisioning, typically 10+ minutes).

Per the user's constraints: "Don't launch local service stacks or execute long-running commands. If the quickstart requires either, be upfront about it and stop."

Omnistrate's quickstart (CLI quickstart at docs.omnistrate.com) requires the following: account signup, CTL installation, configuring cloud credentials (AWS access key/GCP), then omnistratectl deployment of services which provision actual cloud infrastructure — long-running. So it should be stopped, and I should be upfront about it.

Also, Omnistrate doesn't publish a general-purpose SDK on npm/PyPI — they generate per-service OpenAPI SDKs, and the platform API is called directly using a JWT/API key obtained from the account. So even a "light" API-only example (e.g., calling the platform API to list services) requires account credentials, which we don't have here.

Let me quickly check the CLI quickstart docs to back up the cloud account requirement. Fetch the quickstart-with-CLI page under docs.omnistrate.com/getting-started/.

$ curl -s -m 15 -L "https://docs.omnistrate.com/getting-started/quick-start-with-cli/" | python3 -c "{"content":[{"text":" 404 - Not found \n","type":"text"}]}ctrl+o
curl -s -m 15 -L "https://docs.omnistrate.com/getting-started/quick-start-with-cli/" | python3 -c "
import sys,re,html
t=sys.stdin.read()
m=re.search(r'<article.*?</article>',t,flags=re.S)
t=m.group(0) if m else t
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
print(t[:2500])"
Thinking…

Please find the correct URL. Let me get the sitemap or navigation links from the docs home.

$ curl -s -m 15 -L "https://docs.omnistrate.com/sitemap.xml" | grep -o -E "<loc>[^<]+" | sed 's/<loc>//' | grep -i -E "quick|cli|onboard" | head{"content":[{"text":"https://docs.omnistrate.com/getting-started/account-onboarding/\nhttps://docs.omnistrate.com/getting-started/onboarding/aws/\nhttps://docs.…ctrl+o
{"content":[{"text":"https://docs.omnistrate.com/getting-started/account-onboarding/\nhttps://docs.omnistrate.com/getting-started/onboarding/aws/\nhttps://docs.omnistrate.com/getting-started/onboarding/azure/\nhttps://docs.omnistrate.com/getting-started/onboarding/gcp/\nhttps://docs.omnistrate.com/getting-started/onboarding/nebius-vllm/\nhttps://docs.omnistrate.com/getting-started/onboarding/nebius/\nhttps://docs.omnistrate.com/getting-started/onboarding/overview/\n","type":"text"}]}
Thinking…

Hmm, there's no quick-start page in the sitemap matching "quick|cli"? The grep also included "cli"—no match? Weird, the earlier navigation had "Installing CLI", "Quick start with CLI", and "Quick start with UI". Maybe the URLs are different. Let me list all the getting-started URLs.

$ curl -s -m 15 -L "https://docs.omnistrate.com/sitemap.xml" | grep -o -E "<loc>[^<]+" | sed 's/<loc>//' | grep -E "getting-started" | head -30{"content":[{"text":"https://docs.omnistrate.com/getting-started/account-onboarding/\nhttps://docs.omnistrate.com/getting-started/build-from-compose/\nhttps://d…ctrl+o
{"content":[{"text":"https://docs.omnistrate.com/getting-started/account-onboarding/\nhttps://docs.omnistrate.com/getting-started/build-from-compose/\nhttps://docs.omnistrate.com/getting-started/build-from-helm/\nhttps://docs.omnistrate.com/getting-started/build-from-kustomize/\nhttps://docs.omnistrate.com/getting-started/build-from-operators/\nhttps://docs.omnistrate.com/getting-started/build-from-repo/\nhttps://docs.omnistrate.com/getting-started/build-from-terraform/\nhttps://docs.omnistrate.com/getting-started/getting-started-with-ctl/\nhttps://docs.omnistrate.com/getting-started/getting-started-with-web/\nhttps://docs.omnistrate.com/getting-started/installing-ctl/\nhttps://docs.omnistrate.com/getting-started/mcp-server/\nhttps://docs.omnistrate.com/getting-started/overview/\nhttps://docs.omnistrate.com/getting-started/zero-to-saas/\nhttps://docs.omnistrate.com/getting-started/onboarding/aws/\nhttps://docs.omnistrate.com/getting-started/onboarding/azure/\nhttps://docs.omnistrate.com/getting-started/onboarding/gcp/\nhttps://docs.omnistrate.com/getting-started/onboarding/nebius-vllm/\nhttps://docs.omnistrate.com/getting-started/onboarding/nebius/\nhttps://docs.omnistrate.com/getting-started/onboarding/overview/\n","type":"text"}]}
Thinking…

Interesting — there's an "mcp-server" page: "AI Agent Setup". Omnistrate has an MCP server for AI agents. Let's read "getting-started-with-ctl" and "mcp-server" to check the prerequisites.

$ curl -s -m 15 -L "https://docs.omnistrate.com/getting-started/getting-started-with-ctl/" | python3 -c "{"content":[{"text":" getting-started Quick start with Command Line ¶ What is Omnistrate CTL? ¶ Omnistrate CTL is a command line tool that helps you build SaaS …ctrl+o
curl -s -m 15 -L "https://docs.omnistrate.com/getting-started/getting-started-with-ctl/" | python3 -c "
import sys,re,html
t=sys.stdin.read()
m=re.search(r'<article.*?</article>',t,flags=re.S)
t=m.group(0) if m else t
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
print(t[:3000])"

{"content":[{"text":" getting-started Quick start with Command Line ¶ What is Omnistrate CTL? ¶ Omnistrate CTL is a command line tool that helps you build SaaS Products, manage Plans, and operate instance deployments efficiently. Install the CLI before you continue by following Installing Omnistrate CTL . Quick start video ¶ Note: Some features may have been updated since the video was created. Refer to the omnistrate-ctl manual for the most up-to-date information. If you are onboarding hosted cloud accounts or customer BYOA accounts from the CLI, start with the Cloud Account Guides . Build Service from Compose Spec ¶ Before you can build a SaaS Product, you need a Compose specification that defines the product. The Compose specification file should include the Plan configuration in the x-omnistrate-service-plan section. For more information on creating a Compose specification, refer to the Compose spec reference . To build a service from a compose spec file, use the build command with the following information: --file : The path to the compose spec file (optional will default to omnistrate-compose.yaml, docker-omnistrate-compose.yaml, or spec.yaml) --product-name : The name of the service to create. --description (Optional): A description of the service. --service-logo-url (Optional): The URL of the service logo. --release (Optional): Flag to release the service. This will make the Plan available to create instance deployments. --release-as-preferred (Optional): Flag to release the service as preferred. This will make the service the default version used to create instance deployments. --environment (Optional): The name of the environment where the service will be built. Default is the dev environment. --environment-type (Optional): The type of environment where the service will be built. Use together with the --environment flag. Default is the dev environment. --interactive (Optional): Flag to enable interactive mode for building the service. This will prompt you to access your Customer Portal and promoting the Plan to production. omnistrate-ctl build --file omnistrate-compose.yaml --product-name \"Your product name\" --interactive Automation and build behavior notes ¶ For CI or other non-interactive workflows, you can log in by piping the password over stdin: cat ~/omnistrate_pass.txt | omnistrate-ctl login --email [email protected] --password-stdin Keep the following build behaviors in mind: --environment must match the configured environment name exactly. If omitted, build targets the Dev environment. Use --environment-type together with --environment so the service plan resolves to the intended environment identity. When you release a build, include --release-description so the resulting Plan version is easier to audit later. If the rendered spec is unchanged, Omnistrate may reuse the existing Plan version instead of creating a new one. Use --force-create-service-plan-version only when you explicitly need a new released version for identical inputs. If you change\n","type":"text"}]}
$ curl -s -m 15 -L "https://docs.omnistrate.com/getting-started/mcp-server/" | python3 -c "{"content":[{"text":" Configuring Omnistrate MCP Server ¶ Connect your AI tools to Omnistrate using the Model Context Protocol (MCP) , an open standard that let…ctrl+o
curl -s -m 15 -L "https://docs.omnistrate.com/getting-started/mcp-server/" | python3 -c "
import sys,re,html
t=sys.stdin.read()
m=re.search(r'<article.*?</article>',t,flags=re.S)
t=m.group(0) if m else t
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
print(t[:2500])"

{"content":[{"text":" Configuring Omnistrate MCP Server ¶ Connect your AI tools to Omnistrate using the Model Context Protocol (MCP) , an open standard that lets AI assistants interact with your Omnistrate services and infrastructure. What is Omnistrate MCP? ¶ Omnistrate MCP is Omnistrate's official MCP server. It is a local MCP server that gives AI tools secure access to your Omnistrate projects and resources through the omnistrate-ctl command-line interface. It integrates with popular AI assistants like Claude, enabling you to: Search and navigate Omnistrate documentation and knowledge base Manage services, environments, and service plans Create and manage instances and deployments Monitor service health and operational events Manage subscriptions and customer access Configure deployment cells and cloud accounts Analyze costs and audit logs Connecting to Omnistrate MCP ¶ To use Omnistrate MCP, you need to have omnistrate-ctl installed and configured on your system. The MCP server communicates with Omnistrate through your local CLI installation. Prerequisites ¶ omnistrate-ctl CLI tool installed and in your PATH Omnistrate account with appropriate permissions Authentication configured for your Omnistrate account Supported clients ¶ Omnistrate MCP can be integrated with various AI tools and IDEs that support the Model Context Protocol: Claude Code Claude.ai and Claude for Desktop Cursor VS Code with Copilot Cline Windsurf Gemini Code Assist Gemini CLI Setup the MCP Server ¶ Connect your AI client to Omnistrate MCP and authorize access to manage your Omnistrate infrastructure. Claude Code ¶ # Install Claude Code npm install -g @anthropic-ai/claude-code # Configure Omnistrate MCP Server claude mcp add --scope user omnistrate omctl mcp start # Start coding with Claude claude Claude.ai and Claude for Desktop ¶ Custom connectors using remote MCP are available on Claude and Claude Desktop for users on Pro, Max, Team, and Enterprise plans. Open Settings in the sidebar Navigate to Connectors and select Add custom connector Configure the connector: Name: Omnistrate Command: omnistrate-ctl mcp start Cursor ¶ Add the snippet below to your project-specific or global .cursor/mcp.json file: { \"mcpServers\" : { \"omnistrate\" : { \"command\" : \"omnistrate-ctl\" , \"args\" : [ \"mcp\" , \"start\" ] } } } Once the server is added, Cursor will attempt to connect. Ensure your Omnistrate credentials are configured. VS Code with Copilot ¶ Installation ¶ Enable the mcp server with one command: omnistrate-ctl mc\n","type":"text"}]}
Thinking…

Now the full picture is clear:

Omnistrate is a platform for ISVs to build and operate SaaS/PaaS products. Developer workflow:

  1. Sign up for an Omnistrate account (email/password, free trial).
  2. Install omnistrate-ctl (Go binary).
  3. Onboard a cloud account (AWS/GCP/Azure) with actual cloud credentials — required to deploy anything.
  4. Create a compose/spec, build the service with omnistrate-ctl build, and deploy instances (provisioning actual infrastructure — long-running).

There's no generic public SDK on npm/PyPI. The API (api.omnistrate.cloud) uses JWT login with account credentials, and per-service customer-facing SDKs are generated from OpenAPI. There's an MCP server but it wraps the CLI and needs an authenticated account.

Blockers here:

  • Omnistrate credentials aren't provided (no env vars). Signing up creates a third-party account and requires interactive email verification. Even after signup, there's nothing meaningful you can do without an AWS/GCP account for onboarding.
  • The quickstart essentially provisions actual cloud infrastructure — long-running — and requires your own cloud account credentials. Per the user's constraints, I have to state this frankly and stop.

Could I do "light" parts: install omnistrate-ctl and write a sample compose spec + build command without deploying? That's possible, and arguably executable. But without an account, the sample can't be validated. User's instruction: "If this product has no developer workflow you can operate, state so frankly and stop." The workflow exists but can't be operated without credentials and cloud accounts. Honest answer: state it's blocked, explain the reason, provide pricing, provide an ease-of-management assessment. Optionally, leave a small scaffold behind? The user said "if the quickstart needs one of those, state so frankly and stop." Quickstart needs long-running deployment and cloud credentials → stop. Shouldn't build a partial scaffold. Keep it clean. Actually, writing an unvalidated compose spec might be marginally helpful, but instructions say stop. State frankly and stop. Minimal artifacts — probably no files needed. Keep the repo clean.

Pricing summary (from omnistrate.com/pricing):

  • Starter: $100/month per active deployment, includes deploy to customer environments, BYOC/on-prem, private-label portal, SSO/RBAC, etc. Basic support included; Standard support add-on minimum $999/month.
  • Growth: vCPU-hour-based pricing (per-deployment option also available), contact us; adds hosted SaaS tenancy, metering/billing/Stripe, day-2 automation.
  • Enterprise: custom pricing.
  • 1-month free trial, no credit card required.
  • Note: Infrastructure costs are separate — you pay your own cloud (or your customer's cloud in the BYOC case); Omnistrate charges platform fees. Active deployment = a running instance of your service being managed by Omnistrate (there's an anchor definition on the page; can confirm, but generally = a non-stopped deployment instance).

Ease of management for me (the agent): mixed. Positive: declarative compose-based specs, CLI with non-interactive login (password-stdin), CI-friendly flags, official MCP server for AI agents, REST API. Negative: everything requires a human-owned account and cloud provider credentials, deployments are long-running infra provisioning, no public SDK packages, feedback loops are slow (deploys take minutes+), debugging needs console access. Conclusion: easy to create specs and automate via CLI/API once authenticated; can't operate autonomously end-to-end in this sandbox.

Response format: concise, frank stop statement first or last. Structure:

  1. Verdict: stopped — reason.
  2. What Omnistrate is / what the quickstart needs.
  3. Pricing.
  4. Ease-of-management assessment.

I researched Omnistrate (docs, pricing page, API endpoints, npm/PyPI) rather than building, and I'm stopping per your constraints. Here's the situation plainly.

Verdict: blocked — stopping as instructed

Omnistrate is a platform for ISVs to turn software (Docker Compose, Helm, Terraform, K8s operators) into a distributable SaaS/PaaS offering. Its quickstart cannot be done "light":

  1. No public SDK. There is no omnistrate package on npm or PyPI (I checked — 404s, and npm search returns zero results). You interact via the omnistrate-ctl CLI or the REST API at api.omnistrate.cloud, both of which require an authenticated Omnistrate account. Per-service SDKs are generated for your customers from OpenAPI specs — they're outputs of the platform, not a way into it.
  2. No credentials here. Nothing in this environment provides an Omnistrate account, and signup is a web flow (email verification / OAuth). I won't create third-party accounts unprompted.
  3. The quickstart is inherently heavy. Even with an account, the documented flow (docs.omnistrate.com/getting-started/) requires onboarding a real AWS/GCP/Azure account with your cloud credentials, then omnistrate-ctl build + instance deployment, which provisions real cloud infrastructure and runs for many minutes. That fails both of your rules: it needs cloud credentials I don't have, and it's a long-running deployment. There is no meaningful read-only or sandbox API surface to demo without all of that.

One notable positive: Omnistrate ships an official MCP server (omnistrate-ctl mcp start) designed exactly for AI agents like me — but it just wraps the CLI, so it has the same account + cloud-credential prerequisites.

How pricing works (from omnistrate.com/pricing)

  • Starter — $100 per active deployment per month. A deployment is a running instance of your service that Omnistrate manages; includes customer-cloud/on-prem delivery, private-label customer portal, upgrades/pipelines, SSO/RBAC/audit logs, AWS Marketplace fulfillment. Basic support included; Standard support is a $999/mo minimum add-on.
  • Growth — vCPU-hour based pricing (per-deployment pricing also available; contact sales). Adds hosted-SaaS tenancy models, BYOC/BYO-VPC, usage metering, billing/invoicing with Stripe, day-2 automation (scale, backup, failover, drift detection).
  • Enterprise — custom pricing, custom SLAs, compliance reports, multi-cloud marketplaces.
  • 1-month free trial, no credit card. Key point: Omnistrate only charges the platform fee — underlying infrastructure is billed by your cloud provider (yours or your customer's, in BYOC), and Omnistrate is never in the customer data path.

Would it be easy for me to manage?

Partially — good ergonomics, but not autonomously. In favor: declarative compose-style specs with an x-omnistrate-service-plan section, a CI-friendly CLI (non-interactive login via --password-stdin, deterministic build flags), an OpenAPI-documented REST API, and a first-class MCP server for agents — clearly built with automation in mind. Against: every action requires a human-owned account plus real cloud-provider credentials, feedback loops are slow (minutes-plus infra provisioning, not seconds), and debugging wants console access. So: once you supply an authenticated account and cloud onboarding, I could comfortably author specs, run builds, and drive deployments via CLI/API/MCP. From a bare sandbox like this one, I can't act on it at all.

No files were created; the repo is untouched.

AX Fundamentals

23 checks. Open an area for details.

This check is a quick preview. Test more tasks and models with Gauge Agents.

Test your product with Gauge Agents

AX Check by Gauge