At this point we have 6 microservices written in go in the appliance: - team-server probe: already mentioned in the blog post. Determines if any installe

At this point we have 6 microservices written in go in the appliance: - team-server probe: already mentioned in the blog post. Determines if any installed Team Server is down. - ca: as mentioned in the blog post, as simple Certificate Authority - charlie: a checkin service. Desktop clients periodically post to it to signify they are up. This data is used in each user's device list to show if the device is up and which ip it was last seen from. - auditor: takes audit event in an HTTP endpoint and forwards them to a raw TCP connection as expected by splunk and co - valkyrie: a relay server used for data transfers when desktop clients cannot establish direct TCP connection (more about that in a future blog post) - lipwig: a messaging/pubsub server used for peer discovery and notifications (more about that in a future blog post)