> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/getting-started/operating-models.md). # Operating models: Hosted and Standalone Differences between Hosted customers (supported by a provider) and Standalone customers (their own equipme license). equipme is used in two operating models. Operation is the same in both; some features and responsibilities differ. | | **Hosted** | **Standalone** | | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | | **What is it?** | The company uses equipme via a **provider** (IT service provider, reseller or lessor) that makes its offering available in the Marketplace. | The company has its **own equipme license** and organizes its portfolio and suppliers itself. | | **Registration** | Via the provider's portal address or created by the provider | Directly with equipme | | **Marketplace** | The provider's offers (and, where applicable, cross-provider offers it has released) as well as your own services | Your own services, offers from connected suppliers and from your own offline suppliers | | **Branding, terms and conditions, privacy policy, legal notice** | Come from the provider; your own theme is possible | Your own theme | | **Ordering permission** | Must be granted by the provider | Available immediately | | **Suppliers page** | Only if enabled by the provider; offline suppliers only | Always available: connected suppliers, invitations, offline suppliers | | **"Invite supplier"** | – | ✓ | | **Custom links** (your own menu links) | – | ✓ | | **Trial period** | – | ✓ (at the start) | | **Add-on modules** | Enabled by the provider | According to license | ## Hosted customers As a Hosted customer, you are permanently connected to **one** provider. The provider delivers the services, processes your orders and supports you. In equipme, you see the status of your orders and assets in real time, without email ping-pong. ### Ordering permission for Hosted customers Newly registered Hosted customers are initially **not allowed to order**. This is how the approval works: 1. On your first attempt to order, **"Request order approval"** appears with a note that you first need to accept the provider's contract terms. 2. After you submit, the status reads "Your request for order approval is currently being processed!" 3. The provider reviews the request and grants the approval. 4. You receive the message "You have been activated for order approval …". **Log out and log back in once** so that the permission takes effect. ### What the provider controls for you Your provider enables the following features for your company. If you need one of them, contact your provider: * Ordering permission and automatic order confirmation * Pre-orders * Equipme Operate ticket system * HR sync * Internal inventory (your own services and recording of existing devices) * Supplier management (offline suppliers) * Billing module (invoices) * Automation module ## Standalone customers As a Standalone customer, you use equipme with your own license. You build your own [service portfolio](/dokumentation/offer-management/service-portfolio.md) and obtain services * from **connected suppliers** who use equipme themselves and with whom you are connected via **Partner Connect**, and/or * from **offline suppliers** that you maintain yourself in equipme and whose orders you process manually. Learn more under [Suppliers](/dokumentation/offer-management/suppliers.md). When you register, automatic order confirmation, HR sync and the Equipme Operate ticket system are already active. {% hint style="info" %} **Trial period:** Standalone companies start with a free trial period. A banner shows the remaining days. When it expires, the app is locked until you have booked a plan. To do so, contact equipme via "Contact us". {% endhint %} ## Frequently asked questions **How can I tell which model we use?** If your Marketplace contains a provider's offering and the terms and conditions and legal notice (user menu → "Info") come from that provider, you are a Hosted customer. If in doubt, your administrator can ask support. **Can we, as a Hosted customer, also order from other suppliers?** Partnerships with other equipme suppliers are reserved for Standalone customers. If your provider has enabled supplier management, you can maintain **offline suppliers**. **We can't change the company name.** For Hosted customers, the company name can only be changed as long as no order exists yet. After that, the provider can help. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hub.equipme.io/dokumentation/getting-started/operating-models.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.