Enterprise-ready
Your infrastructure. Your sign-in.
On-premises deploymentSingle sign-on (SSO)Available on request
Control where Emargen runs
and what agents can do.
Bring agents into your organisation with confidence. Your people stay in control, with the visibility and authority to own the decisions they make.
Run Emargen on your infrastructure.
Emargen supports on-premises deployment and single sign-on. Where the application runs and where AI requests are processed are separate parts of the setup.
AI processing
Your model configuration.
Choose providers and models for chats and agent jobs, using your own provider accounts or a gateway managed by your IT team.
Include every model route in the deployment review.
How model configuration worksThe admin agent and initial repository scan currently use Emargen-selected models. On-premises hosting alone does not make AI processing local.
Know what becomes available to agents.
Sharing inside Emargen and access to connected systems follow different rules. Both matter when you decide which knowledge to make available.
Emargen records
Access follows the person.
A connected assistant acts as one person in one organisation. It can access the Emargen records available to that person, through the tools it has been allowed to use.
Connected tools
Choose the account and sources deliberately.
Each connection uses one account for the organisation. Information that account can read may appear in anyone's answer. Connect an account scoped to knowledge everyone in the organisation may access.
Code repositories
Choose which code to make available.
Emargen keeps a copy of each repository you add, so agents can inspect the code and analyse it. People in the organisation can read those repositories and their analyses.
Share the findings.
Keep each conversation private.
Start a private topic, then choose who can read or take part. People you share with see its document, files, comments and versions. Each person's chat with the agent remains private.
Ana's chatPrivate to Ana
One shared topicFindings · Sources · Decisions
Tom's chatPrivate to Tom
Choose who reads and who takes part.
Give someone Reads to ask questions and comment, or Takes part to change the topic. Only the owner changes who sees it.
Topic sharingAgent Notes stay personal.
Other people in Emargen, including administrators, cannot read your Agent Notes. Turn a useful finding into a topic or initiative when you want to share it.
Explore Agent NotesLet agents act. Keep approvals with people.
Give agents room to investigate, write and carry out tasks. Keep the decisions that approve a plan or change its requirements with the people responsible.
Agents can
Research, prepare and carry out tasks.
- Write topic sections as you talk.
- Run the recurring jobs you configure.
- Prepare requirements, options and proposed changes.
People decide
Approve plans and decide changes.
- Publish and approve initiatives.
- Decide change requests against the agreed plan.
- Give the human approvals required by a flow.
For setup changes such as a new board or field, in-app agents show what will change and ask you to confirm. Scheduled tasks run on behalf of their owner, with the instructions, timing and sharing they set.
How agents act in EmargenControl access. Keep a record.
Assign responsibilities, inspect what changed and decide when support can enter.
Roles and sign-in.
Define who can manage models, invite people or approve initiatives. Single sign-on is available on request, with company roles mapped to Emargen roles.
Single sign-onSources and history.
Check the sources behind findings, numbered next to what they back. A page says whether it is decided, research or a draft, and what could not be found. Topic versions show who contributed, what changed and when. Recorded decisions keep the choice, reason, person and date.
Topic versionsSupport access you control.
Emargen support can enter your organisation only when you enable access. It expires after 24 hours; you can end it sooner. Sessions and changes are recorded.
Support accessCost control
Choose the models. Understand the bill.
Chats are only part of the bill. Scheduled jobs, code analyses and background writing use models too. Emargen makes that usage visible.
Your provider accounts.
Use your own AI provider accounts and pay providers directly, on your terms.
A model suited to the task.
Set defaults for chats and agent jobs. Personas can have their own model and thinking level, so routine questions and demanding reviews can use different configurations.
Usage you can inspect.
Review each month by activity, model, person and initiative, alongside tokens and calls. People who manage models see organisation-wide usage; everyone can see their own.
Let's work through your deployment requirements.
Tell us where Emargen needs to run, which systems it should connect to and who will use it.
Early access · We reply by email.