Teams & enterprise
Everything your team knows,
turned into work it can deliver.
An efficient, low-cost productivity tool for teams and enterprises. Files, meetings, clients and projects enter a long-running work system — answers have sources, tasks finish in the background, people review the results, and finished work flows back into the library. It runs on your own machines by default, with no cloud usage fees.
01 · Not another knowledge base
Retrieval is a component.
So is execution.
What a team needs is a work system that runs for the long term and keeps accumulating. What it manages is the team’s long-term assets, not a single session.
Knowledge base / RAG Q&A
Retrieves answers to one question
One-off agent
Completes one goal or task
OpenMiRA
A team work system that keeps running
Scope
One question
One task
All of the team's files and business history, over the long run
Where answers come from
Retrieved snippets
Whatever context it got this time
Only the team's own files, with a source and scope for every conclusion
How far it goes
Returns an answer
Finishes this one task
Plans, runs long tasks in the background, and delivers reports, sheets, images and video
Who decides
No deliverable involved
Usually ends when it's done
Results are previewed first; a person accepts or sends back
Afterwards
Chat ends; start over next time
The result stays in that run
Back into the library, the start of the next job
Where data lives
Depends on the vendor
Depends on the vendor
On your own device
This compares approaches, not specific products. It has search and execution too; the difference is that both sit inside one long-running process.
02 · What we believe
Teams don't need more answers.
They need work that gets delivered.
These five principles shape everything it does.
01
Your files belong to your team.
It runs locally and your data stays on the device. Original files stay in place, with no migration or format conversion; if you stop using it, your data is left as it was.
02
Every conclusion needs a source.
Answers only from the team’s own files, with sources and limits stated: if it can be checked, it can be trusted.
03
Deliver, don't just answer.
Hand complex tasks to the workbench: it plans, runs long tasks in the background, and delivers reports, sheets, images and videos. No need to watch the whole way; review the result when it’s done.
04
People decide.
Results are previewed first, and people decide whether to accept or send back. The AI only suggests; the final call is a person’s.
05
Every job adds up.
Results return to the library and become the organization’s memory. The team’s experience no longer depends on any one person’s recall.
03 · How it works
Five steps from files to deliverables.
Complete one dependable delivery first, then expand step by step. Contract review, meeting summaries, document organizing and content production are good places to begin.
01
Connect
Contracts, files and meetings come in by business folder and subscription.
02
Understand
Classifies, summarizes and indexes, keeping evidence and relationships.
03
Execute
Runs long tasks in the background, calling tools as planned.
04
Review
Results are previewed first; a person decides whether to accept or send back.
05
Reuse
Results return to the library as team memory.
04 · Available now
Stage by stage,
Already running on a real instance.
01
Library
The team’s files, meetings and client material, in one local index.
→ Structured understanding
LibraryDocuments, images, audio and video in one local foundation.
ConnectorsFolders, mailboxes, web pages and subscriptions sync continuously; originals stay where they are.
02
Knowledge base
Keeps the team’s facts and experience current by business topic, with a source on every conclusion.
→ Grounding and consistency
Knowledge baseBind folders, web pages and subscriptions; kept current by topic.
Daily digests & Q&AAnswers only from this library and cites its sources; harder questions go to the workbench.
Video evidenceAsk by meaning, jump to the clip, add it to the chain of evidence.
03
Creation
Generate documents, sheets, images and video on-device, grounded in the team’s own material.
→ Spec-ready output
WorkbenchSearch → plan → generate docs and sheets → a person accepts or sends back.
Creative studio21 retouching tools, marketing copy, product images.
Video generationText-to-video and image-to-video, with versions and re-creation kept.
04
Publishing
Review, schedule and publish to each platform’s specs, then bring the results back.
↩ Results flow back
Multichannel publishingSpecs for 15 platforms, plus review and scheduling. Nine connect directly; the rest are prepared semi-automatically.
Content calendarPublishing schedule, scheduled digests and prep reminders, in one calendar.
Performance feedbackDirectly connected platforms report 10 metrics automatically; they’re archived and fed back into creation.
ThroughoutTeam home: what’s new, risks and to-dos, every dayResults reviewed by peopleOutbound logging
14,701
files
18
sources
7,288
items indexed
14
subscriptions
A snapshot from a live instance, not demo data
ImprovingThe main capabilities are in place; scenario templates and long-term operations for small teams are still being refined release by release.
05 · Team edition
Multi-user,
separated by role and domain.
One deployment serves the whole team. Every person, group and project gets its own space; data stays isolated between them, and what each person can do is set by role and grant.
Multi-user mode is off by default and is switched on by the owner; personal and family setups never see these controls.
Multi-tenant isolation
Personal, shared and group spaces. Groups are created by an owner, and membership is explicit. Search, Q&A, file access, generation and sharing are all checked against the space at every exit, and the default is deny.
Roles and permissions (RBAC)
Owner and member roles. Fine-grained permissions are granted per action, to a role or an individual, and can be limited to one space; revoking takes effect immediately.
Audit
Grants, capability changes and cloud calls are recorded, and owners can review them.
Quotas and rate limits
A per-user requests-per-minute cap, with owners exempt.
Single sign-on (SSO)
Connects to your company’s OIDC identity provider, with passkeys alongside. It needs a stable HTTPS entry point, so it comes when real enterprise deployments need it.
06 · Content teams
Brand, assets and past work
are team assets too.
For content teams it covers the whole chain of brand, material, production and management — what it manages is complete content production, not a single generation.
Content knowledge base
Brand style, product info and past work ground every generation.
Creative workbench
Posters, product shots, short videos: multi-step creation that keeps the plan, the outputs and team review.
Work & publishing
Versions, rework and reuse in one place; work goes out to multiple channels.
Examples
Examples, generated on-device by OpenMiRA.
07 · Who it's for
Teams whose data can’t leave the building,
and who deliver every week.
Mostly photos, video and recordings, sensitive client data, a fixed delivery every week and no dedicated IT: teams like these benefit first.
Photo & video studios
Hundreds to thousands of photos and videos per job; clients’ faces are sensitive and can’t leave the building
01Point it at the job’s photo and video folder
02Recognizes each client; a person confirms likely matches
03Retouching: day-night and weather changes, local touch-ups, with the original and every version kept
04Make albums and short films
05A person reviews it before it goes to the client
Bookkeeping · tax · law firms
Receipts, contracts and recordings for dozens to hundreds of clients, which can’t go to the cloud
01Bring in a batch of receipts (a folder or a mailbox)
02Extract invoice details and recompute the amounts to check them
03Compile a report
04A person reviews it; anything wrong goes back for rework
05Send through the channel each client prefers
Start with one device and one library.
Nail one frequent task first: prove the value with one delivery you can review, then expand to the whole team.