ar-agents cloud · hosted platform · 2026

The code is open-source. The platform, not necessarily.

Self-hosting ar-agents is free and always will be. But hosting a signed audit log with SLA, AR data residency, key rotation, regulator-ready dashboards, and 24/7 support is serious work. If your AI corporation prefers to consume that as a service, there's a tier for you.

This page answers the question any journalist asks in minute two: “How do you make a living from this if everything is open source?”

Open-core model. The library + RFCs + reference implementation are under MIT + CC-BY-4.0, free forever. What's charged is operation: hosting with SLA, cryptographic key custody, data residency in Argentine territory, legacy-system integrations, and contractual support. Same model as Vercel over Next.js, Resend over nodemailer, Supabase over Postgres, Linear over their public CLI repo.

Self-host

Available

Open source. Forever.

Devs who want to run their own stack

Free · MIT + CC-BY-4.0

  • 17 npm packages under @ar-agents/*
  • 5 CC-BY-4.0 RFCs + test vectors
  • Complete reference implementation
  • Deploy to Vercel / Cloudflare / Deno / any Edge
  • Docs + cookbook + AGENTS.md per package
  • Issues + discussions on public GitHub
  • No telemetry · no caps · no lock-in
Start on npm →

Studio

Preview · waitlist open

Managed hosting + audit pipeline.

AI corporations that prefer not to operate infra

Preview pricing · contact us

  • Persisted audit log with SLA · 99.9% uptime
  • Regulator-ready forensic dashboard (multi-session)
  • Automatic Ed25519 key rotation (RFC-005 § 4)
  • Periodic export to JSON + CSV + ASiC-E containers
  • Automatic conformance monitoring (RFC-002 + RFC-004)
  • Forwarded webhooks with HMAC + guaranteed dedup
  • Email + Slack support, 24h SLO
  • Encrypted backups, 5-year retention (RFC-004 § 7)
Request invitation →

Government

In design · prelaunch

For the Argentine state.

Public agencies · external auditors · LPDP-regulated entities

Bilateral agreement · per-project pricing

  • Data residency in Argentine territory (local datacenter)
  • Signed Law 25.326 DPA + restricted transfer clause
  • Ed25519 key custody in auditable HSM (CABA model)
  • SOC 2 Type II audit + ISO/IEC 27001 roadmap
  • Contractual SLA with penalties + 24/7 support
  • Multi-tenant isolated by jurisdiction
  • Internal training for auditors + advisors
  • Feature roadmap aligned with AAIP, AFIP/ARCA, IGJ
  • Source code under escrow for continuity
Technical meeting →

Bespoke

Available

Turnkey implementations.

Large companies · businesses in migration

Per-project quote

  • Guided full-stack implementation (2-8 weeks)
  • Legacy system integration (SAP, Oracle, AR ERPs)
  • Custom adapters for proprietary tools
  • Migration path from existing stacks (Stripe, Twilio, etc.)
  • Internal tech-team training
  • Post-launch on-call · 90 days included
  • Initial RFC-002+004 audit + remediation plan
Quote an implementation →

Why the code stays open-source

  • Regulatory credibility. A Ministry advisor can't recommend adopting a stack a single vendor controls closedly. Open source = the state can fork it and keep going if the maintainer disappears. That continuity is the reason it's viable to legislate over the infrastructure.
  • Broad adoption. If it were closed, no AI corporation without licensing budget could use it. Open lets the whole ecosystem adopt; payers are those who need SLA, residency, or auditing, not those who can assemble it themselves.
  • Defensibility against capture. If a large consultancy (Globant, Accenture, BGH) decides to enter, they can offer services over the open code but can't close it. The real moat is the maintainer's evolution speed + the closed dashboard, not the license.
  • Compatibility with cite-by-reference. Argentine law can cite RFC-004 with an immutable GitHub commit hash (see /cite). That requires the document to be CC-BY-4.0 and the reference code to be MIT-verifiable.

How it compares to known open-core stacks

ProjectWhat's OSSWhat's paid
VercelNext.js, Turborepo, AI SDKHosting, AI Gateway, KV, Postgres, support
Supabasesupabase-js, Postgres extensions, CLIHosting, auth, storage, dashboard
Resendreact-email primitivesSending pipeline, dashboard, SLA
LinearCLI primitives, integrationsIssue tracking SaaS, enterprise SSO
Cal.comWhole stack open-sourceHosting, white-label, enterprise
ar-agents17 npm packages, 5 RFCs, reference implStudio · Government · Bespoke (this page)

For investors and partners

Today (2026-05-13) the project is in pre-revenue stage: the library is published, the regulatory ecosystem is still forming, and the commercial platform is in design. The revenue strategy is sequential:

  1. Studio ships in preview Q3 2026, once there are 5+ AI corporations seeking managed hosting.
  2. Government requires enacted law + ministerial decision to outsource the infrastructure. Expected Q4 2026 - Q1 2027.
  3. Bespoke is available today for early-adopters building their AI corporation in anticipation of the law.

Email naza@naza.ar if you want to see the full deck, financial model, or coordinate advisory equity in early AI corporations.

Pre-revenue honesty

  • No paying customers yet. Studio + Government are in design. Bespoke received 0 formal quotes to date.
  • One maintainer. Operational continuity is a real risk mitigated by code escrow, CC-BY-4.0 RFCs, and npm provenance, but not eliminated.
  • Government tier depends on variables I don't control. The law may not pass, the ministry may decide to outsource to Globant, the regime may mutate. The commercial model respects that uncertainty.