Compare Unified products side by side.

See the purpose, surface, connectivity, and current boundaries of Unified CRM, Unified POS, and Luma Office.

Product comparison

Different products for different operating contexts.

The products do not require one another. Any connection between products must be scoped and configured for your deployment.

Unified CRM

Best for: Connected customer operations
Primary surface: Browser workspace
Core work: Records, service, invoices, files, projects, portal, and automation
Connectivity: Networked cloud workspace
Data boundary: Configured cloud workspace with role-based access
AI assistance: Eiko assistance and scoped automations
Payments: Invoices and configured Stripe billing/payment sync
Current availability: Scoped customer rollout

Unified POS

Best for: Station-level service and point of sale
Primary surface: Browser/static, Android, and Windows station
Core work: Register, orders, kitchen, tables, shifts, printing, and reports
Connectivity: Core station workflows are local-first
Data boundary: Stored on each station; no shared backend sync
AI assistance: No AI workflow positioned for the current station product
Payments: Records externally approved card tenders; does not process or settle cards
Current availability: Scoped pilot and station evaluation

Luma Office

Best for: Consolidated Windows desktop work
Primary surface: Windows x64 desktop application
Core work: Docs, Slides, Sheets, browser, Eiko, and embedded CRM
Connectivity: Office files are local; web and CRM features use the network
Data boundary: Local office files; embedded CRM has a separate authenticated cloud boundary
AI assistance: Eiko desktop companion
Payments: No payment-processing workflow
Current availability: Windows x64 development build; discuss access directly

Capability	Unified CRM	Unified POS	Luma Office
Best for	Connected customer operations	Station-level service and point of sale	Consolidated Windows desktop work
Primary surface	Browser workspace	Browser/static, Android, and Windows station	Windows x64 desktop application
Core work	Records, service, invoices, files, projects, portal, and automation	Register, orders, kitchen, tables, shifts, printing, and reports	Docs, Slides, Sheets, browser, Eiko, and embedded CRM
Connectivity	Networked cloud workspace	Core station workflows are local-first	Office files are local; web and CRM features use the network
Data boundary	Configured cloud workspace with role-based access	Stored on each station; no shared backend sync	Local office files; embedded CRM has a separate authenticated cloud boundary
AI assistance	Eiko assistance and scoped automations	No AI workflow positioned for the current station product	Eiko desktop companion
Payments	Invoices and configured Stripe billing/payment sync	Records externally approved card tenders; does not process or settle cards	No payment-processing workflow
Current availability	Scoped customer rollout	Scoped pilot and station evaluation	Windows x64 development build; discuss access directly

Before you choose

Choose CRM

When the main problem is customer context, service coordination, client access, and connected operational follow-through.

Choose POS

When the main problem is running an individual service station with local register, kitchen, table, shift, and reporting workflows.

Choose Luma

When the main problem is bringing local office editing, web work, AI assistance, and access to CRM into one Windows desktop.

Tell us what your team needs to run. We will explain the product fit, current limits, and rollout options.