The problem
Cost, infrastructure availability and territorial constraints make remote connectivity larger than a software installation problem.
Connectivity in difficult territories
Astrolink
A Go technical base for investigating low-cost infrastructure and software for internet access in remote areas.
- Role
- Initial architecture, software and documentation
- Period
- 2026 — present
- Status
- Public prototype
Context
The repository is an evolving technical proposal. It organizes hypotheses and software without presenting pending simulation and field validation as finished results.
What was built
Astrolink
- 01
A software base in Go.
- 02
A public structure for the proposal and its technical history.
- 03
A foundation for simulations, network assumptions and validation.
Architecture in 60 seconds
Territory → Network → Software → Validation
- 01
Territory
Range, energy, cost and maintenance constraints
- 02
Network
Connectivity and communication hypotheses
- 03
Software
Services and experiments organized in Go
- 04
Validation
Simulations and field tests still required
Decisions and trade-offs
Start from constraints
Start from constraints
Architecture begins with territory and cost before choosing technology.
Prototype is not production
Status and limitations remain explicit so intent is not presented as a result.
Code and documentation together
The technical proposal remains traceable alongside the evolving software.
Verifiable result
- A public base for evolving the technical investigation.
- A clear separation between proposal, prototype and future validation.
- Implementation history verifiable on GitHub.
Known limitations
- No published field validation yet.
- Range, cost and operation assumptions still need documentation and simulation.
- The project does not claim production-ready connectivity.