The Awala-Internet Gateway is a cloud-native, server-side application that acts as an Awala Internet gateway that connects private gateways to the Internet as well as each other.
This documentation is aimed at people contributing to the development of this app, and organisations operating an instance of this app.
By default, private gateways (e.g., the Android gateway) will connect to an instance of this app operated by Relaycorp, which means that neither users nor service providers have to deploy their own instance – in fact, both stakeholders are encouraged not to do that anyway:
- Unless the Internet gateway is shared with many users, it’d be relatively easy for an observer to identify the user. This is analogous to email addresses: If you have an email address at a domain that only you or very few people use, then an outsider could infer who you are – Which wouldn’t happen if you use a widely-used domain like
- Awala service providers need not be concerned about the Internet gateways of their users, just like Web site operators need not be concerned about the Internet Service Providers (ISPs) of their users.
If you decide to operate a Internet gateway, whether this implementation or one provided by another party, you are strongly encouraged to familiarise yourself with the Awala bindings supported by the gateway. Otherwise, it would be very hard for you to configure it properly or triage issues.