> For the complete documentation index, see [llms.txt](https://help.marcopayroll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.marcopayroll.com/marco-user-guide-x4/2025/introducing-marco-os/marco-service-platform/marco-os-vs.-marco-service-platform-key-differences.md). # Marco OS vs. Marco Service Platform: Key Differences ### **1. Marco OS: The Core Technology** Marco OS is the underlying system that powers multiple platforms, including the **Marco Service Platform** and **white-label vendor platforms**. It provides the essential foundation for: * **User role management** (Vendor, Staff) * **Profile types** (Manager, Worker) * **Authentication and security** * **Data processing and platform-wide services** Since all platforms powered by Marco OS share the same core structure, user roles, permissions, and functionalities remain consistent across different implementations. *** ### **2. Marco Service Platform: The Master Platform** The **Marco Service Platform** (or simply **Marco**) is Marco’s own implementation of Marco OS. It serves as the **master platform** that offers payroll, HR, and operational tools. It includes four key data categories: * **Platform Data**: System-wide configurations, logs, and settings. * **Customer Data**: Company profiles, employee records, and payroll details. * **Partner Vendor Data**: Vendor organization details, assigned customer data. * **Vendor User Data**: Individual vendor user profiles, permissions, and activity logs. The Marco Service Platform follows **the same role structure** as white-label platforms: * **Vendor Admin**: Manages all customers, partners, and vendor settings. * **Vendor User**: Manages assigned customers but has limited platform access. * **Staff Users (Manager/Worker)**: Company employees who interact with payroll and HR services. *** ### **3. White-Label Platforms: Vendor-Branded Implementations** White-label platforms are vendor-specific versions of Marco, powered by **Marco OS**. These platforms: * **Operate under the vendor’s branding** while maintaining Marco OS’s core functionality. * **Follow the same role and profile structure** (Vendor Admin, Vendor User, Manager, Worker). * **Allow vendors to manage their own customers and business settings independently**. Despite being independently branded, **white-label platforms function identically** to the Marco Service Platform. The only difference is that each vendor controls their own instance. *** ### **Key Takeaways** * **Marco OS** is the foundation that powers both the **Marco Service Platform** and white-label vendor platforms. * **The Marco Service Platform** is Marco’s own implementation of Marco OS, acting as the **master platform**. * **White-label platforms** have the same structure but are branded and managed by vendors. * **User roles (Vendor Admin, Vendor User, Staff) and profile types (Manager, Worker) remain the same** across all implementations. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.marcopayroll.com/marco-user-guide-x4/2025/introducing-marco-os/marco-service-platform/marco-os-vs.-marco-service-platform-key-differences.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.