Start the proof of value
Two products, one gate

Govern the cloud you actually run.

Arian proves cloud savings in the bill. Ayra blocks risky changes before they exist. Both read your clouds read-only, draft every fix, and wait for a person to approve it.

Start the proof of value Watch the tour Talk to sales
90 days, no card Read-only until you enable execution Data stays in Azure Central India
01 CONNECTAzureread-only reader02 SCANUnattached diskidle for weeks03 GATEblock · flag · allowFIN-04 cost ruleno security block04 APPROVEFinOps leadtyped confirm05 EXECUTESnapshot firstthen delete06 VERIFY · ALLOWEDSaving measuredin the next bill01 CONNECTAzureread-only reader02 SCANUnattached diskidle for weeks03 GATEFIN-04 cost ruleno security block04 APPROVEFinOps leadtyped confirm05 EXECUTESnapshot firstthen delete06 VERIFY · ALLOWEDSaving measuredin the next bill
CertifiedISO/IEC 27001:2022
CloudsAzureAWSGoogle CloudKubernetesDatabricks
IdentityEntra IDGoogle Workspace
WorkflowSlackTeamsJiraServiceNow
ResidencyData in India
The products

Two questions, two products, one organisation.

Cost and risk are different jobs with different owners. We built a product for each and kept them linked, so a team can start with one and add the other without a second sign-in.

Arian
FinOps by AIFog

Every saving, verified in the bill.

One reconciled number for spend across three clouds, recommendations that carry their evidence, and fixes that go through a gate and a named approver before anything moves.

  • Spend, allocation and data trust across Azure, AWS and Google Cloud, plus Kubernetes and Databricks
  • Meter-level recommendations with provenance, not just VM rightsizing
  • Autopilot for cost with real, reversible execution on your approval
  • Savings measured against the next invoice, never estimated into realized
Explore Arian Start the Arian proof
Ayra
Security prevention by AIFog

Block the change before it exists.

One gate across Terraform, CI, the console and the CLI, scoring 170 guardrails in one decision. A block carries a time-boxed waiver, and every verdict lands in a hash-chained ledger.

  • Native enforcement: Azure Policy deny today, AWS Config managed rules where you enable them, CI blocks on Google Cloud
  • Identity posture from Entra ID, AI and agent posture from Foundry, Bedrock and Vertex
  • Waivers with a signed break-glass link, approver never the requester
  • Drift, compliance mapping and weekly digests your auditor can read
Explore Ayra Start the Ayra proof
+

Better together. Buy both on one organisation and the cost and risk graph, the unified gate and shared Autopilot switch on. One sign-in, a switcher between the two, and a fix blocked by an Ayra guardrail shows up in Arian with the reason.

See what both unlock
Written as what you do

Monday morning, by role.

FinOps lead

You open with the saving that landed.

Not the one that was promised. Arian shows the fixes executed last week and the delta the invoice confirmed, with the ones still pending marked as pending.

Security engineer

You see the public bucket as a blocked event.

With the requester's name and the guardrail that fired, at the moment it was attempted. Not as a finding three days later with no owner.

Platform and SRE

You approve the fix from Slack.

Typed confirmation, blast radius listed, rollback hint attached. The change record writes itself and lands in ServiceNow or Jira SM before the execution runs.

CFO

You read one number for cloud.

Reconciled to the invoice, allocated to the teams that spent it, in rupees or dollars as of the last settled day, with a trust score next to it instead of a caveat.

Read from the platform, not written for the page

The numbers we will put our name to.

170
active guardrails
across security, cost and compliance
3
clouds
Azure, AWS and Google Cloud, plus Kubernetes and Databricks
ISO/IEC 27001:2022
certified
September 2026
5
frameworks mapped
ISO 27001, SOC 2, PCI-DSS, NIST 800-53 and CIS

Each figure is read from the platform's own catalog or from the certificate. No customer counts, no projected savings, no averages from a survey.

How to read an AIFog number

Every figure says how far you can trust it.

Measured

Read from your invoice after the change, against a recorded baseline.

Pending

Executed, and waiting for the invoice that will confirm it.

Estimated

A projection before anything changed. It is never added to a realized total.

Unmeasured or simulated

Labelled, counted separately, and never in the headline.

Each figure in the product names its source and its age. Live appears only with a load inside the last 48 hours, and sample data is always badged.

How it holds together

Three habits, built into both products.

See, understand, trust.

A number without its source is a guess with good typography. Every figure in AIFog names where it came from and how fresh it is, every change passes one gate, and every outcome is sealed into a ledger.

  • Provenance on every KPI. The export, the API, the settled day. A stale number says so.
  • One gate for both domains. Cost rules and security rules return a single verdict: block, flag or allow.
  • A hash-chained ledger. Each entry sealed with the previous hash, tagged with the control it evidences.
SPEND · THIS MONTHOne reconciled numbermatched to the provider invoiceFOCUS exportas of yesterdayGATEallowLEDGER · HASH-CHAINEDapprovedtyped confirmation, named approverexecutedrollback hint recordedverifiedsaving measured in the next bill

Built by you, readable by anyone.

An agent that acts on your cloud owes you its reasoning. Before Autopilot proposes a fix it writes the justification dossier and the change record a reviewer would have written, in the words your CAB already uses.

  • The dossier. Evidence, provenance, blast radius and the twelve objections an owner usually raises, answered or conceded.
  • The change record. Classified, window-aware, with a rollback plan, pushed to your ITSM before anything runs.
  • A named approver. Typed confirmation from a person with the right role, never the requester.
JUSTIFICATION DOSSIERWhy this fix, in evidenceUtilisation30 days, metrics APIProvenanceeach figure names its sourceBlast radiusdependants listedObjectionstwelve common ones, answeredCHANGE RECORDReadable by anyoneCLASSstandard changeWINDOWyour freeze calendarROLLBACKsnapshot, then deletePUSHED TOServiceNow or Jira SM

Move fast, break nothing.

A gate that slows engineers gets bypassed. Ours decides inline with the change and hands back a waiver path instead of a dead end, so the fastest route is also the governed one.

  • Decided with the change. The verdict rides back with the apply, the pipeline step or the portal error. No ticket queue.
  • A waiver on every block. A signed link, a reason, a time box. When it expires the guardrail applies again on its own.
  • Nothing blurred. Blocked at the gate and detected after the fact are labelled differently, always.
CHANGEterraform applyGATEdecided inlineVERDICTBlockedWAIVER · SIGNED LINKRequested with a reasonAPPROVED · TIME-BOXEDExpires in seven daysWHAT YOU DO NOT GETa ticket queuea finding three days latera permanent exception
Enterprise

Built to be trusted with a cloud you cannot afford to break.

Both products run on the same private platform, with the controls an Indian bank's security review asks about on the first call.

Data in India

Processed and stored in Azure Central India. Customer data is not replicated outside the region.

Private by default

No public data plane. Database, AI, storage and logs sit behind private endpoints; admin access runs through a jumpbox that is off when not in use.

Row-level isolation

Row-level security is enforced on every tenant table and the application connects as a non-privileged role. One organisation cannot read another, even through a bug.

A second factor, required

A password with a required authenticator code, or SSO through your own OIDC or SAML identity provider. Seven scoped roles with separation of duties in code.

SOC 2 controls mapped

Every Trust Services criterion is mapped to an operating control in the ISMS. We will list the report the day it is issued, not before.

ISO/IEC 27001:2022

Certified in September 2026 across FinOps, cloud security, governance and remediation. Certificate and Statement of Applicability on request. Trust Center

In place of case studies, until we have ones we can name

What you get in 90 days.

The proof of value is scoped to one outcome per product. Here is the path to it, week by week, with execution withheld until you choose a plan.

Arian
Goal: a saving measured in your bill
  1. Day 1
    Connect one cloud read-only
    A reader role and the billing export. The clock starts here, not at signup.
  2. Week 1
    One reconciled number, allocated
    Spend matched to the invoice, split by team, product and environment, with a trust score and coverage gaps named.
  3. Week 2
    Recommendations with their evidence
    Idle, orphaned and oversized resources down to the meter, each with utilisation provenance and a dossier.
  4. Week 4
    Your first gated approval
    Autopilot drafts the fix and the change record; your approver confirms. During the proof your team applies it with Arian's plan.
  5. Day 90
    A saving verified in the next invoice
    Or you walk away with nothing owed and the workspace kept. Arian moves to Free unless you choose a plan.
Ayra
Goal: a posture scan with findings recorded, and a gate your auditor can read
  1. Day 1
    Connect a cloud or a Prevent source
    A subscription, account or project, or a CI webhook. The clock starts on the first source.
  2. Week 1
    Full posture scan
    Every finding recorded under the guardrail it reports to, with the ones we could not check listed, never counted as passing.
  3. Week 2
    The gate in monitor mode
    Azure Policy published in audit, AWS Config rules where you enable them, CI checks reporting. You see what would have been blocked.
  4. Week 4
    Your first enforce rule
    Usually public storage or open SSH. The first block carries a waiver link, and the first waiver lands in the ledger.
  5. Day 90
    A posture you can show an auditor
    Findings, verdicts and waivers in one hash-chained record. Ayra pauses until you choose a plan; the record is kept.
Who we built this for

Three kinds of buyer, one platform.

Banks and insurers

Data residency in India, private endpoints, separation of duties and an auditor-readable ledger, with ISO/IEC 27001:2022 already held. Native enforcement on Azure for the controls your regulator asks about by name.

Read the Trust Center

Managed service providers

One console across every customer organisation, isolation at the database row, and a monthly report that writes itself from verified savings and gate verdicts. Sell either product on its own or both.

See the partner programme

Platform teams

A gate that returns its verdict with the pipeline step, waivers engineers can request without a ticket, and an Autopilot that writes the change record you would have written. Terraform, GitHub Actions, Slack and Jira in the loop.

How the gate works
Product tour · two and a half minutes

The whole platform, narrated.

Recorded on the live platform in sample-data mode. The figures are illustrative; the workflow is the one your team will use.

Inform spend, allocation, data trust Optimize recommendations, verified savings Prevent the gate, AI and agent posture Autopilot governed remediation
Questions

Before you connect an account.

What is the 90-day proof of value?
Connect one cloud read-only and run either product for 90 days without a card. Arian gives Business access with real execution withheld; Ayra gives Prevent Pro access on the same terms. The clock starts when your first cloud or source connects, not at signup. On day 90 you keep the workspace and everything it found.
Which product do I need?
Arian if the question is cost: spend, allocation, recommendations and savings you can verify in the bill. Ayra if the question is risk: a gate that blocks a bad change before it exists, with waivers and an auditor-readable ledger. Teams that buy both get the fused views and a 20 percent bundle discount.
Does AIFog change anything in my cloud on its own?
No. Connections are read-only until you enable execution for your organisation. Every action is drafted, scored at the gate, approved by a named person with a typed confirmation, then executed with a rollback hint and recorded in the ledger.
Which clouds are supported?
Azure, AWS and Google Cloud, plus Kubernetes and Databricks for cost. Native enforcement runs as Azure Policy deny rules today and as AWS Config managed rules where you enable them; Google Cloud changes are blocked in CI.
Where does my data live?
In Azure Central India, behind private endpoints, with row-level isolation between organisations. Customer data is not replicated outside the region. AIFog is ISO/IEC 27001:2022 certified.
How is this different from a FinOps tool or a CSPM?
A FinOps tool reports cost and a CSPM reports risk, and both stop at the report. Arian carries a recommendation through approval and execution to a saving measured in the invoice. Ayra decides at the gate, before the resource exists, and keeps a hash-chained record of every verdict and waiver.
Design partners

We are looking for design partners.

Arian and Ayra are young products, and the best version of them will come from teams running real cloud. If you have a cost or security problem worth solving properly, build it with us.

Apply to be a design partner
  • A direct line to the people building it, instead of a ticket queue.
  • A real say in what we build next, starting with your hardest problem.
  • Pricing shaped with you, agreed once you have seen it work.
  • In return, run it on a real environment and tell us plainly what works and what does not.
Self-serve

Start the proof of value

A free evaluation: ninety days, no card. Connect one cloud read-only and the clock starts. Pick Arian, Ayra or both at signup, and we agree a price afterwards.

Start the proof of value How pricing works
With us

Talk to sales

Bring your estate and your questions. We walk through both products on your stack and leave you with custom pricing and the paperwork.

Talk to sales Book a demo