Skip to content
AI for the systems your team already uses

Connect your company’s tools. Put AI to work.

Bring company systems, files and everyday conversations into one AI workspace. Start with one workflow, connect the data it needs, and choose the model and deployment that fit your business.

Jobs at risk From question to approved post
Illustration · fictional data
Mei
Which jobs are at risk of missing tomorrow’s deadline?
Wenmio
Checked 2 sources
Two jobs need review. W-104 is awaiting a report; W-109 is missing a required result.Job export · 09:00Report queue · 09:05
Draft · LINE group · Production Only Mei can send

W-104 and W-109 may miss tomorrow’s deadline: W-104 is waiting for its report, W-109 needs a result.

Sent after Mei approved
Posted to Production · 10:42

What Wenmio offers

  • Connect existing systems

    APIs, databases and file exports, assessed during setup.

  • Choose your model

    Local or hosted options, with verified support listed in the availability list.

  • Control deployment

    Deployment and data flow matched to your requirements.

How it works

From scattered information to a useful answer.

Wenmio brings relevant information together, shows where it came from, and helps your team take the next step.

  1. 01

    Ask in plain language

    Someone asks in a supported channel, as they would ask a colleague.

  2. 02

    Retrieve authorized data

    Wenmio reads the sources connected for this workflow.

  3. 03

    Explain with references

    The answer says what it found and which systems and files it used.

  4. 04

    Prepare a draft

    When the next step is a message, Wenmio drafts it for someone to check.

  5. 05

    Approve before it’s sent

    Reading needs no approval. A draft goes out only when the asker sends it. Approval before changes in work systems is planned.

What Wenmio does

Built around the systems you already run.

Wenmio starts from your systems and your team’s questions. The model, and where it runs, are choices that fit around them.

Wenmio on infrastructure you approve

Connect the systems you already have

Start with APIs, databases or scheduled file exports. We assess access and configure the connector.

MCP servers: AvailableWeb APIs: In validationDatabases: In validationFile exports: AvailableMailboxes: In validationNAS folders: In validation
Explore connector setup

Work through familiar channels

Access company workflows through supported chat and app interfaces.

Web app: AvailableDesktop app: AvailableLINE: In validationSlack: PlannedTeams: PlannedEmail: Planned
View channel availability

Choose the model that fits

A tested local model or a supported hosted provider, to fit your tasks and data rules.

gpt-oss 20B: AvailableOllama, vLLM: In validationHosted APIs: In validation
Compare deployment options

Keep people in control

Use scoped access and approval steps for supported actions.

On-site only: AvailableActivity log: AvailableLINE approvals: In validationPer-person sign-in: In validationWrite approvals: Planned
Read the security overview
  • AvailableBuilt and checked. Ready to use in a pilot.
  • In validationBuilt, but not yet proven in a real setup.
  • PlannedNot built yet.

Also in the workspace

File search: AvailableSources shown: AvailableWord and Excel files: In validationProcedures: In validationYour logo: AvailableEnglish, 繁體中文: Available
Connector setup

Your ERP doesn’t need an existing MCP connector to start a conversation.

We assess what your system exposes, then scope a connector and pilot around one useful workflow.

Tell us which system you use
How we connect a system, by the kind of access it offers
System accessProposed approachWhat to know
Documented APIConfigure tools around selected endpoints In validationCoverage depends on API access and permissions
DatabaseApproved read-only account and validated mappings In validationRequires permission and schema review
CSV or Excel exportsSearch or query approved exports AvailableData is only as fresh as the last export
Web interface onlyAssess custom integration workMore fragile; scoped separately

Access, permissions, vendor restrictions and data freshness determine what is possible. Connectors are set up and checked by people, and we confirm what is possible before a pilot starts.

Deployment

Choose where Wenmio runs, and where your data goes.

In both setups the Wenmio server runs on infrastructure you approve. The difference is where the model runs, and so what leaves your network.

Hardware depends on the model, the workload and the deployment. During setup we assess company PCs, Apple silicon Macs, suitable servers and cloud infrastructure. A NAS needs a tested model and configuration first, so it is in validation. Where it has been tested

Local configuration

Available
Inside your network
Staff devices Wenmio server Model server

Wenmio and a tested model run on company-controlled infrastructure, so inference stays inside. We check logging, telemetry, tools and integrations before calling a setup local-only.

Hosted-model configuration

In validation
Inside your network
Staff devices Wenmio server
Outside
Model provider’s API

Each prompt leaves with its context: chat history, file passages, and lookups from systems not kept on-site. What the provider keeps depends on its terms.

In either setup, outside services you use also see their part: LINE, if staff ask there, and cloud systems you connect.

Security and control today

  • Chats and My files are private to their owner; admins can’t open other people’s chats.
  • Saved credentials are encrypted with AES-256-GCM; passwords are salted scrypt hashes.
  • Web API and database connectors only look things up.
  • Systems can be kept to on-site models. LINE posts wait for the person who asked.
  • See activity records lookups and approved posts for 90 days. Wenmio’s code sends no telemetry.

Known limits

  • Plain HTTP, unless it runs behind a reverse proxy or tunnel.
  • Data and backups aren’t encrypted by Wenmio itself; use disk encryption.
  • No approval yet for changes in work systems, so pilots start read-only.
  • No single sign-on, multi-factor sign-in, password reset, audit log or third-party security review yet.

Reviewing Wenmio for your IT team? Email your questions to [email protected]

Pilot

Start with one workflow. Prove it before expanding.

  1. 1Identify one task
  2. 2Assess data access
  3. 3Configure a connector
  4. 4Test with representative questions
  5. 5Train a small group
  6. 6Review results

Connector setup, deployment and ongoing support are scoped separately. Your pilot proposal lists what is included and how success will be measured.

Pricing

Pricing depends on connector work, infrastructure and support.

Request a scoped pilot quote

How we propose to measure a pilot

  • Correct answers on the selected task
  • Time to complete the selected task
  • Weekly staff usage
  • How repeatable the setup is

These are proposed measures, agreed in each pilot proposal. They are not promised results.

Discuss a pilot

Tell us about one task you’d like to improve. We’ll reply by email.

For example: answering order-status questions from the ERP. Please leave out confidential details.

For example: your ERP, a database, Excel exports.

We use these details only to reply about a pilot. Please don’t include passwords, customer data or other confidential information. Sending opens your email app with the request filled in, addressed to [email protected].

or email [email protected]
Evidence

What works today, and what’s still being proven.

We label every feature by what has been checked, not by what we hope. See every feature and its status.

Illustration, not a recording · example data A recording of a real run will replace this once it has been verified.
FAQ

Questions we hear most.

Something else? Ask us when you discuss a pilot.

We assess its APIs, database permissions and exports first. Compatibility is confirmed during scoping, before a pilot starts.

Bring Wenmio to your company.

Tell us which systems your team uses and one task you’d like to improve. We’ll scope a pilot around it.