Dedicated Arc infrastructure for teams that can't share.
Your own Arc nodes, private throughput, residency, a custom endpoint domain and a signed 99.99% SLA, operated by engineers you can talk to. The first call is technical scoping, not a sales pitch.
- nodes
- arc-node execution + consensus, dedicated
- networks
- mainnet 5042 · testnet 5042002
- throughput
- private (provisioned, not contested)
- domain
- rpc.yourcompany.com, managed cert
- residency
- EU-only or US-only
- sla
- 99.99% · credit schedule at /sla
- access
- SSO · RBAC · audit logs
- support
- dedicated channel · engineers on call
Everything in Scale, under one agreement.
The same JSON-RPC, streams and Arc-native APIs, made single-tenant, governed and contractually backed.
Dedicated Arc nodes
Your own Arc execution and consensus nodes, operated by us, used by nobody else. Pinned arc-node versions, upgrades on your change window.
Private throughput
No shared rate limits. JSON-RPC, streams and sinks run at provisioned capacity that no other tenant can contest.
Settlement proof archive
Every commit certificate for the ranges you settle in, cached, signed and delivered to your bucket for the audit file.
Custom endpoint domain and residency
Endpoints on your own hostname with a managed certificate, and EU-only or US-only routing that covers logs and support tooling too.
SSO, RBAC & audit logs
Single sign-on, role-based access, and per-service API keys, with audit logs across every endpoint your organization touches.
Dedicated Slack
A shared channel with the engineers who run the nodes, not a ticket queue. Incidents, questions and schema changes land there first.
White-glove onboarding
We provision endpoints, validate responses side by side with your current Arc provider, and stay in the channel until cutover is boring.
Compliance support
Security overview, DPA, vendor forms and SLA terms ready for review. SOC 2 Type I is in progress and Type II is targeted for Q2 2027; we say so up front.
The fleet behind the endpoint.
Enterprise plans run on dedicated or co-located nodes inside the same architecture that serves the shared tiers, minus the sharing. Same pipeline, private throughput.
Self-operated fleet
We run our own Arc execution and consensus nodes, bootstrapped from Arc's published snapshots, with no upstream provider between you and consensus. Versions are pinned and upgraded on a change window you can see.
Watchdog failover
Per-node health checks demote a lagging node automatically; a warm standby takes its place before your stream notices. Cursors and signed gap reports cover the seam.
Redundant by construction
Ingest and serve layers run redundant paths across regions, so a single machine or region event never becomes your event. Incidents are published with post-mortems.
Everything your procurement team will ask for, in one folder.
Security review, legal, and vendor onboarding move in parallel with the technical evaluation, not after it. Request the pack in the contact flow below and it arrives with the first reply.
Documents are shared under NDA during scoping. Nothing here requires a signed contract first.
From scoping call to cutover in two weeks.
Onboarding is a defined process with a date on every step. You can put it in a planning doc before you've signed anything.
- Week 0
Scoping
A technical call with the engineers who run the nodes: throughput profile, networks, streams and sinks, residency, SLA needs. The procurement pack goes out the same day so security review starts in parallel.
- Week 1
Provisioning
We stand up your dedicated Arc nodes and issue private endpoints and keys. Standard JSON-RPC stays standard: the endpoint changes, your code doesn't.
- Week 2
Side-by-side validation
You run our endpoints next to your current source and compare: responses, balances, transfer counts, certificates. Cutover happens when your numbers say so, not ours.
- Ongoing
Reviews
Quarterly usage and quality reviews cover throughput headroom, cost attribution, and upcoming schema changes. The dedicated Slack channel covers everything in between.
Talk to the engineers who run the fleet.
The first call is technical scoping, not a sales pitch: your throughput profile, filters, history depth, and SLA needs. Two short steps, one business day to a reply.
Prefer email? Write to [email protected]. The same engineers read it.