amal66 gives self-hosted Mike a controlled connectors layer
Firms can link Mike to the information sources their people already use, without giving the platform broader access than each user holds.
amal66 is building two routes into connected work. Where a compatible service can handle its own registration, a team can add it directly. For Google Drive and Slack, the deployment operator sets up the organisation's connection once, then individual users approve access to their own accounts.
- Google Drive: lets a user bring their own readable Drive material into Mike.
- Slack: connects through Slack's hosted AI-tool service, limited to the channels and messages that user can access.
- Other remote tool services: can be added through a common settings flow, including services that use tokens or custom access headers.
The design usefully separates firm-level responsibility, such as app approval and secure hosting, from each lawyer's personal consent. Google and Slack's live approval journeys still need real-world testing, but the surrounding setup and safeguards have been exercised.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?