FAQ

Questions buyers ask, answered plainly.

Hosting, rollout, pricing and support first, then every product. If your question is not here, an engineer will answer it.

Buying, hosting and support

Yes. Each product is complete and sold on its own. Adding a second later activates it on the same tenant, with the same users, permissions and audit log — there is no migration and no integration project.

You choose a US, EU or UK region at tenant creation. Data does not leave the selected region. For buyers with stricter requirements we deploy into your own private VPC and hand over the runbooks.

A typical first department is live in six to ten weeks: two weeks of discovery and data audit, three to four weeks of configuration and migration, then a supervised pilot before wider rollout.

Yes. SAML 2.0 and OIDC, tested against Microsoft Entra ID, Okta and Google Workspace, with SCIM provisioning where your identity provider supports it.

Yes. Import runs through CSV and the REST API, with a field-mapping workshop during discovery. Historical tickets, asset registers and document archives are all in scope.

The named engineers who ran your rollout. Working hours overlap US Eastern and Central European time, and we do not subcontract engineering or support.

Per product and per seat, quoted in USD, EUR, GBP or AED against a written scope. Implementation is quoted separately and your discovery sprint fee is credited against it.

We build it. Every MaeOne product is written and maintained by our own engineers in Chennai, and the person who answers your support thread is one of them. There is no subcontractor and no white-labelled third-party product underneath.

Through a written master service agreement and order form in English, invoiced in USD, EUR, GBP or AED by wire or SWIFT. We work on your paper where you prefer it, sign your NDA and data processing agreement, and name the governing law and jurisdiction in the contract.

You export everything in open formats — CSV for records, original files for documents, JSON for the audit trail — and we assign the IP created for you at handover. The pilot agreement carries a written exit clause, so the first commitment is small and reversible.

Unified Intelligence

Overview →

No. It works through the same permissions, licences and data scopes as the rest of MaeOne. Search is filtered before it runs, and it never reports how many records exist that the person cannot see.

No. It drafts and shows exactly what would change, and a person confirms. Anything that needs approval when a person does it still needs approval, and critical actions are never available to it.

Retrieved content is treated as information, never as instruction. Because permissions are enforced outside the model, even a successful prompt injection cannot exceed what the person asking is allowed to do.

It says so plainly and names what is missing. It does not guess, and it does not reveal what the data would have shown.

MaeOne Asset

Overview →

Yes. One register covers IT and non-IT asset classes, scoped by site, department and asset class, with AMC contracts and warranty dates tracked on every record.

A native agent on Windows, macOS and Linux endpoints reports serial number, manufacturer, model, processor, memory and operating system, and flags endpoints that have stopped reporting in.

Yes. The installable field app works offline for stock takes, site audits and transfers, and syncs back when the device reconnects.

MaeOne Desk

Overview →

Yes. IT, HR and finance requests run in separate queues on one ITIL-aligned desk, with SLA targets set per category and breach warnings before they slip.

Through the self-service portal, email, in-app intake and the REST API. Kanban and list views run over the same dataset.

With MaeOne Asset, the ticket arrives with the asset's specification, warranty status, AMC contract and repair history, and the resolution notes write back to the asset record.

MaeOne People

Overview →

It holds the payroll inputs — leave, attendance and the employee data payroll needs — on the employee record. The payroll calculation itself stays in your payroll system.

The onboarding checklist raises provisioning tickets in Desk, books issued equipment against the employee in Asset and files the signed contract through Doc. The exit checklist reverses all three.

Yes. Leave and claims are self-service on the web and in the installable app.

MaeOne Pulse

Overview →

No. Pulse samples endpoint and web activity into focus hours, application categories, project time and idle patterns, under a collection policy the employee can read.

Reporting defaults to team level. Individual views are permission-gated, so only the roles you authorise can open them.

Measured time is attributed to the tickets in Desk and the projects they belong to, and capacity is reported against the team structure in People.

MaeOne Reach

Overview →

Yes. Pipeline stages are configured per sales motion, with a weighted forecast view, quotes, renewals and contract dates.

Contacts, opportunities, quotes and activity history — and, with the rest of the suite, the tickets raised in Desk, the contracts extracted by Doc and the assets deployed at the customer's site.

Yes. Sign-in uses SSO, and roles can be scoped to territories.

MaeOne Doc

Overview →

Each document type runs as its own auditable pipeline — insurance forms, discharge summaries, KYC packs, contracts, purchase orders and invoices among them — configured with a no-code rule builder.

Confidence scores per field. Values below the threshold you set go to a reviewer; the rest pass straight through.

Yes. Cost and OCR time are reported per task, so you know what each document type costs to process.

MaeOne Endpoint

Overview →

No. Endpoint is sold on its own. Licensed alongside Asset, Network, Desk or People it adds custody, network location, incidents and joiner–leaver context to the device record; without them those sections are simply absent.

Windows first. macOS and Linux are supported capability by capability, and the console shows what each platform supports instead of assuming parity.

Not in this release. Mobile device management, application allow and deny lists, USB control and OS imaging are outside its current scope.

The agent verifies every command itself: the signature, the device it is meant for, the time window, a one-time nonce and its own local allow-list. A command that fails any check is refused and reported as a security event.

Hardware, installed software, network interfaces, security posture and device health. It never collects file contents, keystrokes, browser history, personal messages or camera and microphone input, and it counts network volume without recording destinations.

Yes. Endpoint can import device inventory and compliance from Intune, read-only, so you see one fleet. Commands, deployments and remote sessions need the MaeOne agent on the device.

MaeOne Network

Overview →

No. Network is sold on its own: discovery, monitoring, topology, alerts and notifications all work alone. Endpoint, Asset, Desk and People add managed status, ownership, incidents and affected people when they are licensed.

Scans run only inside scopes you authorise, at the rate you set — 200 packets a second by default — connect-only and limited to your port list. Each scope records who authorised it, so a flagged scan can be traced.

No. It backs up configurations read-only and detects changes, but it never pushes configuration, shuts a port or rolls back in this release.

Its devices show as unknown and one collector-offline alert is raised — no flood of device alerts, and no downtime counted against those devices. With an HA pair the peer takes over; a collector cut off from the cloud stores and forwards up to 24 hours of data.

No. Flows are aggregated into five-minute summaries without payloads, URLs or DNS queries, and end-user devices never show destinations. Packet capture and deep inspection are not part of the product.

Per monitored network device. Devices that are only discovered are not counted, and a device already managed by the MaeOne Endpoint agent is counted once.

Still have a question?

Ask it on a call with the engineers who build the product. Book a demo

One connected platform.
See it in action.

A 30-minute live demo on a data model like yours.

A named engineer replies within one business day.