Presto
Presto is Gateway’s Blockchain as a Service product for supported Besu, Arbitrum, OP Stack, Polygon CDK, and Gateway Stack deployment paths. Candidate interoperability choices—including AggLayer, Hyperlane, Chainlink CCIP, sovereign interoperability, and Ethereum Economic Zone (EEZ)—are evaluated and scoped per network.
- What it is
- Blockchain as a Service
- Current posture
- Available for scoping
- What varies
- Architecture, providers, operating scope, and commitments
Deploying a chain is the first step. Making its authority operable is the product.
An institutional network needs explicit choices for execution, settlement, data availability, proving, bridges, keys, administrators, residency, recovery, change, and support. Presto turns those choices into a defined deployment path.
Keep the core authoritative.
- Workload requirements
- Institutional governance
- Operating controls
Change the capability at a controlled boundary.
Presto changes the boundary, not the institution’s authority.
Architecture before automation
Select compatible components and trust assumptions before treating deployment speed as success.
Authority by design
Define governance, administrator powers, upgrades, keys, participant policy, and institutional responsibilities.
Operations after launch
Scope observability, resilience, change, incident, recovery, support, and exit with the network topology.
What Presto contributes. What still needs a decision.
Stack and topology selection
Configure a supported Besu, Arbitrum, OP Stack, Polygon CDK, or Gateway Stack deployment path according to the workload, topology, and trust requirements.
Component compatibility
Select compatible software versions, settlement, data-availability, proving, bridge, and infrastructure components.
Institutional controls
Map governance, administrators, keys, access, data, residency, change, and evidence requirements.
Interoperability choices
Evaluate candidate asset, message, and data paths using AggLayer, Hyperlane, Chainlink CCIP, sovereign interoperability, or Ethereum Economic Zone (EEZ), with compatibility, dependencies, and operating scope confirmed for each deployment.
Readiness validation
Test performance, failure, recovery, security assumptions, and operational handover against agreed acceptance criteria.
Operating envelope
Define any managed operations, support coverage, service levels, exclusions, and exit requirements contractually.
Continue from Presto into the operating model.
Bring the requirement. Define the Presto boundary.
A focused workshop maps the target capability, existing systems, providers, controls, and deployment variables.