A reusable foundation.
These capabilities guide MeruOS development. Discovery establishes which components can be reused, what needs building and how the result will be evaluated.
NUXISAI / HOME ↗The foundation behind
MERUOS / THE PLATFORM FOUNDATION
The foundation behind
the agents.
Specialised workflows need connections, business context, execution and oversight. MeruOS is the shared platform foundation Nuxis is developing around that work.
Discuss your workflowYOUR SYSTEMS
Applications · Records · Documents
MERUOS FOUNDATION
Context · Execution · Controls
SPECIALISED WORKFLOWS
Customer operations · Finance · Internal services
01 / UNDERSTAND THE OFFERINGDESIGN, DELIVERY & DEVELOPMENT DIRECTION
Your workflow, agreed.
Required connectors, available components, new development, data handling and acceptance criteria are confirmed in the proposal before implementation.
Built progressively.
The Agent Factory and AI Product Manager are internal systems intended for progressive development. They are described on our About page.
Explore the development direction ↗02 / THE PLATFORMONE FOUNDATION. MANY SPECIALISED WORKFLOWS.
MeruOS↗
The infrastructure
behind the agents.
Customer service, finance, sales, and internal operations need different agents. MeruOS provides a shared foundation for their connections, business context, execution, and oversight.
MERUOS / CONNECTPLATFORM DESIGN
Work with the systems your business already uses.
Approved access brings the information and actions needed for a workflow into MeruOS. The integration approach is scoped around the software, APIs, files, and access available in your environment.
- Connect required ERP, CRM, accounting, email, and internal systems.
- Map relevant records and define permitted read and write actions.
- Scope credentials and access to the workflow’s actual needs.
THE PURPOSE
A defined connection between the workflow and its source systems.
REUSE THE FOUNDATION. CONFIGURE THE BUSINESS LOGIC.
Engineers still shape each workflow. The aim is one reusable product, supporting separate customer environments with their own data, permissions, and configuration.
03 / START WITH YOUR EXISTING SYSTEMSINTEGRATION FEASIBILITY / ASSESSED PER WORKFLOW
Your work already
lives somewhere.
We assess the systems, records and permissions a workflow needs before committing to an integration. The examples below are systems to discuss, not a catalogue of ready-made connectors.
Email & documents
Microsoft 365 · Gmail · PDFs
Bring requests and their supporting information into a workflow.
ASSESSED DURING SCOPING
Mailbox permissions and document formats reviewed.
Spreadsheets & records
Excel · Google Sheets · CSV
Use the records your team already maintains.
ASSESSED DURING SCOPING
Data structure, quality and access reviewed.
CRM & customer work
Salesforce · Zoho CRM · Other CRMs
Relate enquiries, customer history and proposed record updates.
ASSESSED DURING SCOPING
API availability and permitted actions reviewed.
Finance & ERP
Tally · Accounting tools · ERP
Check invoices, purchase records and approval requirements.
ASSESSED DURING SCOPING
Connector feasibility and posting controls reviewed.
Team communication
WhatsApp Business · Teams · Slack
Assess where requests, reviews and notifications should happen.
ASSESSED DURING SCOPING
Official APIs, account access and policies reviewed.
No production connector availability is implied. We confirm what is feasible, what needs development, and what access you must approve in your proposal.
04 / CUSTOMER CONTROLQUESTIONS TO ANSWER BEFORE IMPLEMENTATION
Your systems.
Your operating boundaries.
The controls required for an engagement are documented in its scope and verified through evaluation. Ask for the evidence relevant to your workflow.
Which information can the workflow use?
Agree the permitted sources, records and actions. Use approved access and keep customer environments separate.
What can happen without a person?
Define action limits and approval gates before implementation. Financial, sensitive or customer-facing decisions need the authority agreed for that workflow.
What happens when the answer is unclear?
Agree clarification, escalation and stop conditions. Give an unresolved case an owner instead of silently treating it as completed.
How will the team review the work?
Specify the inputs, source references, decisions and action records needed for review, together with access and retention requirements.
Who approves a new version?
Evaluate representative cases and regressions, review release readiness and agree recovery steps before changing a live workflow.
What happens at handover or exit?
Agree access ownership, documentation, data export or deletion, licences and support responsibilities in the engagement scope.
05 / CONTROL IS PART OF THE DESIGNYOUR OPERATION. YOUR BOUNDARIES.
Useful autonomy starts
with clear limits.
MeruOS is intended as one reusable platform with separate customer environments. Each company’s data, permissions, and configuration belong within its own boundaries.
SHARED PLATFORM CAPABILITIESMeruOS
CUSTOMER ENVIRONMENT ASeparate by design.Company dataPermissions & accessWorkflow configuration
CUSTOMER ENVIRONMENT BSeparate by design.Company dataPermissions & accessWorkflow configuration
Illustration of intended environment separation.
Permission before access.
Define the information and actions required for the workflow. Configure access around that scope.
Approval where it matters.
Designate decisions and actions that require employee review. Route unclear cases to a person.
History behind the result.
Track workflow actions, exceptions, and intervention so the team can understand what happened.
Review before release.
Evaluate proposed changes against examples. Keep business-rule changes and production releases controlled.
DEPLOYMENT REQUIREMENTS / AGREED DURING SCOPING
Where should the workflow and its data live?
We agree hosting, access and retention requirements before implementation. These are options to assess, with availability confirmed for the proposed workflow.
START WITH ONE WORKFLOWBring us the work.
Tell us your workflowBring us the work.
Let’s find the next step.
A recurring task, the systems around it and a person who knows how it works.