Atlas Relay

atlasrelay.org connects Internet researchers who need RIPE Atlas measurement credits with Atlas users who have credits to spare. Researchers post a project, and donors send credits in one of two ways. Donors can transfer through the RIPE Atlas API with a single-use key that holds only the credit permissions the site needs, and the pledge is normally confirmed as soon as RIPE accepts the transfer. Donors can also transfer by hand on atlas.ripe.net, and the researcher then confirms receipt. Once the credits are spent, the researcher can post a short write-up of the results with a link. People sign in with GitHub, Microsoft, Google or ORCID.

Credits are donations. Nothing is bought or sold, and donors get nothing in return. The site never holds credits or long-lived API keys, and every transfer happens in RIPE Atlas.

Atlas Relay is a community project and is not affiliated with or endorsed by the RIPE NCC.

Run it locally

Needs Node 24.11 or later and Azure Functions Core Tools v4 (func) on your PATH; see CONTRIBUTING.md.

npm install
npm run dev        # http://localhost:4280 (SWA emulator + API + Azurite)

How it is built

A React single-page app on Azure Static Web Apps, with its API on an Azure Function App (Node 24, Flex Consumption plan) linked to the site, and data in Azure Table Storage, which the API reaches with a managed identity instead of a key. All Azure resources are defined in Bicep under infra/ and deployed as one deployment stack per environment by scripts/bootstrap.sh and scripts/provision.sh. GitHub Actions deploys the site and API from main using OIDC, with no stored Azure credentials. Pushes that touch only docs or infrastructure deploy nothing, and pull requests only build, test and lint.

• docs/ARCHITECTURE.md: design and API
• docs/RIPE-ATLAS-NOTES.md: what RIPE Atlas allows for credits and transfers
• docs/RUNBOOK.md: deploying your own instance and operating it

Contributing and security

Issues and pull requests are welcome; see CONTRIBUTING.md. Please report security problems privately, as described in SECURITY.md, rather than in a public issue.

Licensed under the MIT License.

Third-party notices

The site serves its own copies of two fonts, both under the SIL Open Font License 1.1: Inter (license) and JetBrains Mono (license). The license text also ships in each font's @fontsource package.