← Opportunities

2025 Algorand Relay Program

Funder
Algorand Foundation · Algorand Relay Program ⚪ No history
Type / status
rfp · closed
Amount
—
Deadline
2025-02-24 (past)
“The final date for accepting submissions will be February 24th, 2025.”
Ecosystems
algorand
Categories
infra
Tech stack
Apply
https://docs.google.com/forms/d/1P_UTpEPoTHt3nP8H_dRA-CgWKzgnFNbtEmvGEfmHV8I
Source
https://forum.algorand.co/t/2025-algorand-relay-program/14134
Fit
8% · poor fit · The Venture23 Aleo team works exclusively in the Aleo ecosystem with Rust/Leo/ZK tech, while this Algorand RFP requests general node providers for a relay network with no ZK or privacy focus, making them an outsider to the funder's typical portfolio.
Trust
99% · model self-report 95% · first seen 2026-10-24 · v6
Verified
2026-10-27 · by extraction

The Algorand Foundation is seeking node providers for its Relay Program running from April 1, 2025 to March 31, 2026. Two types of nodes are needed: Non-archival Relays (16 vCPU, 32GB RAM, 256GB NVMe, 100TB/month egress) and Archival Non-Relay Nodes (8 vCPU, 16GB RAM, 4TB SSD + 100GB NVMe, 10TB/month egress). Providers must submit cost proposals per region via Google Form or email. Selection prioritizes cost efficiency, geographic distribution, self-hosted or smaller cloud providers, and willingness to accept payment in ALGO tokens.

Eligibility: Node providers meeting hardware specifications for Non-archival Relays or Archival Non-Relay Nodes, with preference for self-hosted/smaller cloud providers, global geographic distribution, cost efficiency, and acceptance of ALGO token payments.

Pipeline

Override status:

Funder track record · does Algorand Foundation actually pay grants?

⚪ No payout history found · checked 2026-10-30 · 0 forum reports, 10 web pages read, 8 unverifiable claims dropped

Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.

Trust breakdown (3/3 checkable facts verified)

SignalWeightResultNote
deadline0.35100%quoted in source
apply link0.075100%link in source
funder0.075100%named in source
source quality0.1550%social or search hit
model confidence0.195%model self-report
corroborationbonus+10%6 sources

Fit breakdown (against the ORG_* profile)

SignalWeightResultNote
model fit0.510%model rated 10%
ecosystem overlap0.250%algorand vs aleo
category overlap0.1517%infra vs zk, privacy, infra, dev_tooling, security, interoperability
tech overlap0.10%none vs rust, leo, zk

Sources (6)

RoleDocumentFromFetched
primary2025 Algorand Relay Program - General - AlgorandWeb discovery: ecosystem sweep2026-10-24
mirror2024 Algorand Relay Program - General - AlgorandWeb discovery: ecosystem sweep2026-10-24
primary2025 Algorand Relay Program - General - AlgorandWeb discovery: ecosystem sweep2026-10-24
mirror2024 Algorand Relay Program - General - AlgorandWeb discovery: ecosystem sweep2026-10-24
mirror2024 Algorand Relay Program - General - AlgorandWeb discovery: ecosystem sweep2026-10-27
primary2025 Algorand Relay Program - General - AlgorandWeb discovery: ecosystem sweep2026-10-27

History (6)

vChangedFields
62026-10-27title, summary, deadline
52026-10-27summary
42026-10-24title, summary, deadline
32026-10-24title, summary, deadline
22026-10-24title, summary, deadline
12026-10-24created

Extracted text

[![](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/48.png)](/u/shane-at-algo)

[shane-at-algo](/u/shane-at-algo) [Algorand Foundation](/g/Algorand_Foundation)

[Feb 2025](/t/2025-algorand-relay-program/14134 "Post date")

# [](#p-34672-introduction-1)Introduction

As Algorand progresses towards implementing a peer-to-peer gossip protocol, the Relay Program is undergoing a significant directional shift. Traditionally, Algorand nodes require relays for intercommunication, embodying a classic hub and spoke model. The forthcoming peer-to-peer architecture, however, will facilitate direct communication between nodes, rendering the use of relays less critical, though they will remain operational for specific use cases.

# [](#p-34672-future-role-of-relays-2)Future Role of Relays

While relays will continue to play a role, their usage is expected to diminish. They will be particularly vital for users prioritising speed, functioning akin to an express pass. Anticipating the reduced demand post peer-to-peer implementation, the number of relays will accordingly be adjusted.

# [](#p-34672-request-for-proposals-rfp-for-program-participation-3)Request for Proposals (RFP) for Program Participation

We are initiating the RFP process for potential participants, focusing on two types of node providers:

****Non-archival Relays:****

*   16vCPU
*   32GB RAM
*   256 GB NVMe SSD disk
*   100 TB/month egress
*   1 Gbps low-latency connection

****Archival Non-Relay Nodes (gossip services disabled):****

*   8vCPU
*   16GB RAM
*   4TB SSD disk (for blocks and catchpoint storage, referred to as “ColdDataDir” in our configuration)
*   100 GB NVMe SSD disk (for “hot, performance-critical data”)
*   10 TB/month egress
*   1 Gbps low-latency connection

The term of the program would be beginning the 1st of April 2025 lasting to 31st of March 2026.

# [](#p-34672-selection-criteria-4)Selection Criteria

In evaluating proposals for the Algorand Relay Program, the Foundation will prioritise the following key factors:

****Cost Efficiency:**** Proposals will be assessed for their cost-effectiveness, ensuring optimal utilisation of resources.

****Geographical Distribution:**** The geographical location of nodes is critical. A globally distributed network of nodes is sought to enhance the resilience and reliability of the network.

****Hosting Provider Preferences:**** A preference is given to self-hosted setups or smaller cloud providers and data centers. This approach is intended to reduce dependence on major cloud service providers like AWS, Azure, and GCP, thereby mitigating potential risks from policy changes that could affect network operations.

****Payment in ALGO Tokens:**** The Foundation favours arrangements where providers accept payments in ALGO tokens, calculated based on a 30-day trailing average. While this is preferred, it is understood that such an arrangement may not be feasible with all providers.

The Foundation is committed to fostering a robust and decentralised network, and these criteria are designed to ensure the selection of partners who align with this vision and can contribute effectively to the network’s stability and growth.

_****Quality and Performance Expectations****_

Node quality and performance should consistently meet our specified requirements. The contractual agreement will outline minimum operational expectations. Failure to adhere to these standards may result in expulsion from the program.

# [](#p-34672-submission-guidelines-5)Submission Guidelines

Prospective participants are hereby invited to submit detailed proposals outlining the cost structure for each relay node, segmented by region. Submissions should comprehensively detail the financial implications, including any potential discounts for managing multiple relay nodes.

# [](#p-34672-submission-process-6)Submission Process

Proposals may be submitted via the designated [Google Form](https://docs.google.com/forms/d/1P_UTpEPoTHt3nP8H_dRA-CgWKzgnFNbtEmvGEfmHV8I) or, alternatively, directly via email to [shane.mcgovern@algorand.foundation](mailto:shane.mcgovern@algorand.foundation). We encourage early submissions to facilitate thorough evaluation and allow time for any necessary clarifications or inquiries regarding the proposals.

# [](#p-34672-deadline-for-submissions-7)Deadline for Submissions

The final date for accepting submissions will be February 24th, 2025. Prompt submissions are encouraged to ensure adequate time for review and discussion.

  

448 views 7 likes 1 link

 [![](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/48.png "Shane McGovern") 2](/u/shane-at-algo "shane-at-algo")

  [![](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/titi/48/3632_2.png "Titi")](/u/Titi "Titi")

  [![](https://avatars.discourse-cdn.com/v4/letter/z/d26b3c/48.png "ZaqzaqAq21")](/u/Zapmine "Zapmine")