Give each department an assistant in Slack, Teams, Google Chat, WhatsApp, Telegram or your intranet. It runs inside your own cloud, answers from your documents and cites the page every answer came from.
For organisations with 200 to 5,000 staff. Your first department live in 14 days.
Only the question and the passages needed to answer it leave your cloud. Point Emly at a model you host and nothing leaves at all.
Each department gets its own assistant, its own documents and its own admins. HR can't see IT's runbooks, and every answer links back to its source.
My VPN keeps dropping when I'm on hotel Wi-Fi. What should I do?
Switch the VPN client to TCP mode under Settings → Connection[1]. If it still drops, raise a ticket and I'll pass along your device details[2].
How many days of parental leave do I get, and when do I need to tell my manager?
Full-time staff get 16 weeks of paid parental leave[1]. Tell your manager and HR at least 8 weeks before your planned start date[2].
A client wants to give me a gift worth about €150 to say thanks. Can I accept it?
Gifts over €100 need approval from your line manager and must be logged in the gifts register within 5 working days[1].
Illustrative examples. Your assistants answer from your own policies and documents.
The security pack covers each of these in detail, with the architecture diagram, components and network flows for your reviewers.
Where is our data stored?
In your own cloud account or data centre. Documents, the search index, conversations and the audit log all sit in storage and databases you control.
Which third parties receive our data?
Only the language model endpoint you configure. Documents are indexed by an open-source embedding model running inside your deployment. Use a model you host yourself and no third party receives anything.
Who can see conversations and settings?
Only the people you grant access. Admins sign in through your identity provider over OIDC, such as Microsoft Entra ID, Okta or Google. Each assistant has its own owners, admins and viewers.
Is there an audit trail?
Yes. Sign-ins, permission changes and configuration changes are written to an audit log that your admins can review.
How are API keys protected?
Encrypted at rest with a key you hold. Each assistant's model key is stored encrypted and is never shown again after it's saved.
Is our data used to train models?
Emly does not train any model. How your model provider treats requests is set by your own agreement with them, which is one reason we use your API key and not ours.
Can we inspect the code?
Yes. Emly is open source. Your team can read every line, run its own scans and keep running it if we part ways.
We start with one team, prove it on their real questions, then add departments one at a time.
We agree the first department, its documents and the success measures. Your security team gets the architecture write-up.
We install Emly in your environment, connect your identity provider and model endpoint, and hand over admin access.
We index the department's documents and test the assistant on 30 real questions from that team, fixing gaps as we go.
The team uses it in Slack, Teams, Google Chat, WhatsApp, Telegram or the intranet. We review what people asked and which answers need better sources.
After the first departmentAdd more departments as separate assistants, each scoped and priced on its own, with an optional monthly Care Plan that reviews unanswered questions and fixes the gaps.
Tell us a little about your setup. We'll send the security pack and suggest a time for a 30-minute scoping call.
Any model with an OpenAI-compatible API. That includes OpenAI and Azure OpenAI, and open models you serve yourself. Each assistant can use a different model.
Yes, if you host the language model inside your network. The embedding model and search index already run in your deployment. We'll confirm the details for your environment on the scoping call.
Compliance depends on how a system is deployed and operated, so we don't claim certifications. Because Emly runs inside your infrastructure, it sits under the controls, hosting region and agreements you already have. The security pack helps your team assess it.
The first department is a fixed-price setup that we quote after the scoping call. There's no per-seat licence, so adding staff costs nothing extra. You pay your model provider directly.
You keep everything. The software is open source and runs in your cloud, so your team can keep operating it or hand it to another partner.
Get the security pack, then scope your first department on a 30-minute call.
