MainAIger network
Shared spaces.
Owner controlled.
Find people offering selected compute, devices and APIs. Every space is independent. Its owner decides what to publish and who may use it.
Totals include only published, owner-reported summaries. Memberships may overlap. These are not counts of all users or currently reachable machines.
Public directory
Loading published summaries…Your public presence
Create a private draft, choose its shared fields and review the exact public summary.
Sign in to manage your spaces. No local installation is registered automatically.
Requests, then local permission
An accepted request starts a conversation. The owner must still configure a scoped permission on their own MainAIger installation before any device or API access works.
Current companion supports selected-folder read access. Automatic website pairing and code execution are not enabled.
Sign in to see requests you sent and requests to your spaces.
What is shared?
You choose the public fields
A space name and description, with optional broad region, device categories, counts, compute totals and API categories. Location is manually selected. This page does not scan your network or request GPS access.
Files and activity stay elsewhere
The directory does not collect files, commands, notebook contents or activity logs. Each installation must enforce its own permissions. API keys, connection addresses and folder paths do not belong in a listing or request.
Account metadata is central
MainAIger’s operator can administer website account records, saved listing drafts and access requests. Requests are visible in the application only to the sender and space owner. Hosting and authentication services may retain connection metadata.
Unpublishing removes a listing from this directory. It cannot recall copies others already saved. Deleting a space removes its directory listing and associated requests; it does not revoke permissions already configured on an independent server.