Introduction to Awacs
Next-gen behavior analysis server (think Mixpanel, Google Analytics) with built-in encryption supporting HTTP2 and gRPC. Node.js, headless, API-only, horizontally scaleable.
We take security seriously in Awacs. We believe that security & privacy is a human right, and should be done properly.
Every active application in Awacs has a unique authorization token to tell the server where the information belongs to. This token is sent using the x-socketkit-key HTTP header. It's recommended to have an SSL certificate in between the client and server to make it harder for an attacker to read the application authorization token.
It's required that every request sent to Awacs public API should be signed with ed25519 on the client side. This digital signature algorithm enables us that the information did not get manipulated in the transit between client and server. Signed payload is sent through the
x-signature HTTP header.
We have a variety of SDKs for Awacs and additionally support OpenAPI auto-generated SDKs.
Contributing to Awacs
We welcome every contribution to Awacs with love. Please read our CONTRIBUTING guide for more details.