Personal AI Assistant
Model selection is configuration rather than a compile-time constant: each request is routed to the model designated for its tier.
-
Privacy
Data remains on your infrastructure
- Deployed on infrastructure you own and administer, not on a third-party service.
- Calendar, document and scheduling data are processed on that host and are not transmitted.
- Requests classified as private may be routed to a locally hosted model, so the payload does not leave the host at all.
-
Efficiency
Inference cost scales with difficulty
- Each request is classified into one of four tiers — simple, normal, difficult, private — and routed to the model designated for it, so the premium model is invoked only where the request warrants it.
- The classification threshold for each tier is configurable, which is the mechanism for keeping load off the expensive tier.
- A tier may be bound to a locally hosted model, removing per-token cost for that class of request entirely.
- Expenditure is metered rather than estimated, attributed to the routing decision that incurred it, and subject to a per-user cap.
-
Security
Bounded, not trusted
- Credentials are injected into outbound requests by the tool layer and never enter the model context, so no conversation can disclose one.
- Outbound access is confined to an explicit egress allowlist, which only an operator may extend.
- No inbound mail is processed and no public listener is exposed: sender addresses are trivially forged, so untrusted input is not accepted as instruction.
- Expense approval cannot be delegated to unattended execution; confirmation is required from the user on every occasion.
- A single command places the deployment in read-only mode, refusing all writes while reads continue.
-
Single-tenant per user
Data, credentials and quotas are isolated per user; no shared store spans them.
-
Confirmation before side effects
Reads execute automatically. Any action that contacts a third party, incurs expenditure or mutates a host is queued for confirmation.
-
Provenance-tracked memory
Every retained assertion records its origin, and ingested content is never promoted to an assertion.
Fifty-five capabilities, granted per user — and growing
Each capability is an explicit entry on that user's own authorisation pane, grouped under one of twelve categories. No capability is implied by a role.
- Email and calendarMail, files and chat
- Documents and filesMail, files and chat
- Picture archiveMail, files and chat
- ERPThe business system
- Business system administrationThe business system
- Sandboxes and copiesThe business system
- Business system telemetryThe business system
- Reports and dashboardsReporting and measures
- Report maintenanceReporting and measures
- AutomationCode and automation
- CoolifyCode and automation
- ExpensesThe business system
- Filing expensesThe business system
- Approving expensesThe business system
- Ninety.ioReporting and measures
- Work on a scheduleTheir day
- Work in the backgroundTheir day
- Reporting what it cannot doCode and automation
- Web search and pagesThe web
- Portals it signs in toThe web
- CamerasBuildings and devices
- Home automationBuildings and devices
- The networkBuildings and devices
- Doors and entryBuildings and devices
- Team chatMail, files and chat
- Their own computersBuildings and devices
- Computers they look afterBuildings and devices
- Fixing those computersBuildings and devices
- Code repositoriesCode and automation
- Company knowledge baseMail, files and chat
- ProjectsProjects
- Updating a projectProjects
- Who is on a projectProjects
- Quarterly conversationsMail, files and chat
- Booking a conversationMail, files and chat
- Their working dayTheir day
- Open loopsTheir day
- ListsTheir day
- Trips and bookingsTheir day
- What it remembersWhat it keeps
- Forms and checklistsThings they hand it
- Watching for a changeTheir day
- People it keeps notes onWhat it keeps
- MeetingsMail, files and chat
- Its own instructionsItself
- Meeting notesWhat it keeps
- What it didWhat it keeps
- Spreadsheets they uploadThings they hand it
- Pictures they uploadThings they hand it
- A folder of documentsThings they hand it
- Flight statusThe web
- Places and weatherThe web
- Sleep and readinessHealth and wellbeing
- Its own manualItself
- Adding toolsItself
Further applications
Ordicura Expense Management
Corporate card expenditure from transaction through receipt capture, coding and approval to the accounting export.
Ordicura CRM
Leads, contacts, activities and a sales pipeline, with orders and quotes created in Business Central.
Projects
Multi-party project state — current work, schedule variance and next actions — shared with internal and external participants.
Picture Index
Retrieval over a photographic archive too large to inspect manually.
Ordicura IT Portal
Devices, licences, handovers and helpdesk tickets, filled from Microsoft 365, with a portal for every employee.
Individual for your business
Developed to your specification and maintained thereafter.
Get in touchEngineering principles
-
Security
Access is granted explicitly and narrowly. No part of a system holds more than its task requires, and nothing is permitted merely because it was convenient.
-
Privacy
Data stays with the business that owns it. What is collected is what the work requires, and anything leaving is a deliberate decision.
-
Efficiency
Nothing is entered twice. Data is taken from the system that already holds it, and a manual step is removed rather than relocated.
Get in touch
Enquiries regarding the work are answered here.
Responses are model-generated; verify anything material.
Draft: the page carries no name, address, number or link, so
the assistant above is the only way in. Where the deployment has a mail key, it
can also take a message and pass it on by email. See docs/DRAFT-NOTES.md, which also says what the
assistant needs on your own server. An imprint and a privacy notice are still
required before this goes live, and both will need details the page does not
currently have.