Option 1 : Set up the @platform with free @signs

Create and run your own @platform with free @signs

3 minute read

Getting @signs and keys.

Your first step is to get a couple of @signs, it is best to get at least two, so you can experiment with sharing end-to-end encrypted data across the @platform.

There are two methods to get @signs.

The first

Go to atsign.com and clicking Get an @sign. If you go this route then you have more influence on your free @sign or pay for one of your choosing. Once you have your @signs, do not forget to activate them.

activate @sign

Activating creates a microservice (we call the secondary server) and once that is spun up on The @ Company infrastructure you will see a QR-Code to scan with an @ enabled application.

activated @sign

The pairing consists of your device creating cryptographic keys and sharing the public keys to the secondary server, you will be asked to store your private keys. Storing your keys is vitally important as only you have the keys.

The second

The experience of getting a @sign via the website is great for developers as you have advanced options available, to reset @signs and to point your @sign to your own infrastructure. For getting people onboarded quickly, a better experience would be to get a free @sign within the app itself, this is option 2.

generate @sign

The onboarding widget together with an API key provides a button marked “Generate Free @sign”.

generate @sign-pair

When selected a number of free @signs given to chose from, once selected it is quickly activated, then once again you will be asked to store the cryptographic keys for the @sign.

Once you have your @signs and keys

You are ready to start using the @platform! We have a number demo apps that are constantly being updated, feel free to fork or clone and try them. There is also another nice app in development by xavierchanth which is a chat app using the @platform. It is a nice example to follow as it uses the contacts combined with the at_chat_flutter widgets to create a simple chat app between @signs.


Each @ enabled application will ask you once for your @sign and then your keys, so it can synchronize with your secondary server. This means you might like to store your keys on a personal network drive or service (e.g. gdrive/idrive/onedrive) so you can connect other @ enabled apps to your @sign easily. Remember not to share and protect your keys.

Other widgets and the @platform/@protocol source code

We have an ever-growing number of widgets on pub.dev The @plaform and the @protocol are open source projects on GitHub. If you see something missing, or not working let us know or better still contribute with a PR!