Skip to content
Emily for organizations

Persistent context for the AI experiences you build.

Emily brings a memory layer to conversations and connected tools. Use Emily directly or discuss a branded experience for your organization, with deployment choices and access boundaries defined for your needs.

Give your work a history

Keep project decisions, preferences and useful knowledge connected across conversations. Emily’s memory is separate from the model, so supported model changes can build on the same stored context.

Recall can be incomplete, including in a fresh session or when using selected context. Check the retrieved sources before relying on an answer. Reliability improvements are in development.

A saved record, a retrieved source and a correctly grounded answer are different outcomes. A live continuity demonstration will be published after those steps pass evaluation.

Illustrative continuity example · fictional project · prototype receipt

Project: Harbour launch

Release criterion: the accessibility review must pass before launch.

Source
Fictional release brief, section 2
Contributor
Example connected assistant A
Submitted
16 October 2026, 09:00 UTC (example)
Review state
Attributed, unverified DATA
Correction
Owner review still required
Persistence
Illustration only; no live write or retrieval shown

A later question should retrieve the criterion and its source. This example describes the intended flow; it is not a passed retrieval test.

Choose how you connect

Use the product directly or connect an approved application. Each interface has its own access requirements and limitations.

Available

Web

Use Emily through the product website. Account access and demo limits are separate from a paid subscription.

Explore Emily
Documented

MCP

Connect a compatible assistant. A protocol connection does not establish support for every client or model.

MCP connection guide
Invite-only

SDK

SDK and package access is currently by invitation. Contact us about access and the current package and documentation.

Request SDK access
Documented

Companion API

Connect each person to their own Emily Companion using an approved application and server-side credentials.

Developer guide
Documented

Email

Follow the email guide for account setup and supported use. Check the current plan for included access.

Email connection guide
Alpha testing

Android

Emily’s Android app is in alpha testing.

Ask about the Android alpha

Connection support and subscription entitlements are separate. Review compatibility evidence and plan details.

Bring knowledge from the tools you use

Compatible connected assistants can contribute attributed information. A contribution can be stored as unverified DATA; submission does not make it a confirmed fact.

Teaching permissions in development

Owner-controlled teaching permissions are still in development. Teaching here means saving context, not training model weights.

Keep a clear source, contributor, time and review state with each contribution. A suggestion should remain distinguishable from a confirmed fact. Failed or missing writes must not be described as learned.

Know where information came from

Review the source and state of a memory, check corrections, and verify the evidence used in an answer. A confidence score is not proof that a statement is true.

Illustrative memory explorer: a memory graph and details panel. Screen values illustrate the interface and are not customer results.
Illustrative memory explorer. Memory counts and scores are illustrative; these screens do not prove retrieval reliability.
Illustrative memory connections: a memory graph and details panel. Screen values illustrate the interface and are not customer results.
Illustrative memory connections. Memory counts and scores are illustrative; these screens do not prove retrieval reliability.

Plan the complete deployment

The model provider, Emily memory service, user interface and execution tools are separate parts of the system. Review each data path and operator before choosing a configuration.

Available

Hosted service

Inference
The model configured for the service; a third-party provider may process chats.
Memory, files and logs
Emily conversations, memory, files and account data are stored in Canada. Confirm log retention and subprocessors in the deployment review.
Outbound dependencies
Network access, sign-in, model providers and any connected tools. Review each external data path.
Credentials and operations
Robson operates the hosted Emily service. Applications keep per-user credentials server-side; monitoring and support boundaries must be documented.
By agreement

Organization-controlled deployment

Inference
Choose the model location and provider during the deployment review.
Memory, files and logs
Specify locations for memory, files, backups and logs in the agreement.
Outbound dependencies
Inventory outbound model, authentication, licensing, update and tool connections.
Credentials and operations
Agree credential custody, monitoring, support and operational responsibility before deployment.
Evaluation proposed · release unverified

Local-model evaluation

Inference
Evaluate inference on the selected local hardware and runtime.
Memory, files and logs
Verify memory, files, logs and backups separately from the inference host.
Outbound dependencies
Local inference alone does not establish on-device residency or offline operation. Check every external dependency.
Credentials and operations
Agree who manages models, runtime updates, credentials and monitoring; confirm the supported configuration.
Planned · verification required

Isolated deployment

Inference
Proposed local inference inside an isolated environment.
Memory, files and logs
Document all storage and transfer paths for the proposed environment.
Outbound dependencies
Installation, authentication, licensing, updates and offline operation require verification before an air-gap claim.
Credentials and operations
Define operator access, credential rotation, monitoring and recovery. No verified isolated configuration is offered here.

Canadian storage does not establish that all inference or connected tools operate in Canada. An organization’s jurisdiction does not automatically exclude foreign model processing.

Your workflow, your interface

Discuss a branded experience with access boundaries and operational responsibilities defined for your organization.

  1. 1

    Define the workflow

    Agree supported tasks, account scope, hosting location and API origin.

  2. 2

    Approve each connection

    Each person approves an application through Emily’s hosted device authorization flow.

  3. 3

    Keep credentials server-side

    Your backend resolves the signed-in person’s connection and their own Companion target.

  4. 4

    Validate the outcome

    Check stream completion, saved context, retrieval and answer use. Include recovery and human review.

Custom-interface messages are software-sent; they are not native owner input. The documented Companion API does not grant access to arbitrary clones or administrator tools.

Availability at a glance

Use the status beside each capability when planning your evaluation. Planned work has no promised release date.

Available
  • Web conversations
  • Persistent memory and memory review
  • Connected contributions through supported interfaces
In development / evaluation
  • Android app — alpha testing
  • Recall reliability improvements — in development; deployment evidence pending
  • Local-model deployment — evaluation proposed; release status unverified
Planned
  • Owner-approved, scoped teaching grants
  • Multi-stage autonomous workflows
  • Model selection and bring your own key
  • Companion Plus and Developer tiers
  • Top-ups and add-ons
  • Isolated deployment — verification required
Public offer · owner review pending

Companion · CAD 45 per month before applicable taxes

Review the current allowance, included connections and billing details before subscribing.

Review plans

Evaluate Emily for your organization.

Tell us which workflow you want to support and whether you need hosted or organization-controlled deployment.

Or email sales@robsoninc.com