Run PolariStar for your own customers
PolariStar was not written only for companies deploying it inside a single organisation; the service provider mode is not a bolt-on module but built into the product. We are forming a limited number of partnerships with IT firms that support, maintain and operate infrastructure for their customers.
A service provider’s day looks nothing like a single company’s day: you may touch tickets, devices and networks belonging to five different customers before lunch. PolariStar’s Operations Centre was built for exactly that — every customer lives in a separate workspace, data stays apart, and you work from one cockpit. You are also not obliged to roll out a full installation per customer: you open a workspace from the Operations Centre and, when live visibility into the customer LAN is needed, place a thin collector on site. The product was written inside our own field operation and is used there every day, so the questions your customers will ask are not new to us. The programme is early stage and selective; the goal is not a long partner list but maturing in the field alongside a few partners.
Operations Centre — the partner’s cockpit
You see your whole book of customers on one screen: workspace count, support customers, enrolled devices and agents, and shares waiting for your review. Each row in the tenant list is a separate data area. Adding a customer, attaching a licence and inviting an administrator all happen here.
An isolated workspace per customer
Each customer works inside their own workspace; requests, devices, inventory and users belong to that workspace. Isolation is not a matter of hiding menu items — access control is enforced in the API and query layer. A user at one customer cannot see another customer’s records, nor your cost and profit data.
A workspace and a thin collector, not a full install
Onboarding a customer does not mean shipping a server and standing up the whole product. The default path is opening a workspace from the Operations Centre. If devices on the customer LAN need live monitoring, a small collector goes on site, runs the SNMP scan locally and pushes results into that customer’s workspace. Time to onboard stays short and field cost stays low.
The customer owns the inventory; sharing needs your approval
Each customer collects inventory inside their own area. That data is not copied into your operations area by default. The customer selects what they want to share and sends it to you; you accept or decline it in the sharing queue. Because ownership stays with the customer, this is an easier conversation to have at the contract table.
On-premise and data sovereignty
PolariStar can also run inside the customer’s own environment. You can offer that to customers who will not let data leave the country, who operate on isolated networks, or who are required to keep records on their own servers. Deployment uses signed container images; no source code or signing key is placed on the customer server.
Windows agent and network discovery
A Windows agent for endpoints, TCP/SNMP discovery on the network side, LLDP/CDP topology drawing and threshold based alerts are part of the product. The enrolment key of the specific customer is embedded when the agent MSI is built, so devices land in the right workspace. The monitoring screen’s wall display mode suits a customer NOC screen.
Turkish interface, local team
The interface runs in Turkish, agent installation included. Service provider and organisation surfaces use separate vocabularies: the same screen says “request” and “department” on your customer’s side and “ticket” and “customer” on yours. The team building the product is in Turkey and works in the same field.
A demo environment for sales conversations
Demo mode opens from the address bar and runs entirely in the browser — it writes nothing to the server and contains no real customer data. You can move between the operations, organisation and end user portal surfaces. That lets you show a prospect the product before any installation exists.
Onboarding your first customer
-
Open the workspace
In the Operations Centre you start the “open portal area · attach licence” flow. The first step is choosing the customer: link an existing record if the company is already among your support customers, or open a new one by name.
-
Attach the licence
The second step attaches a licence to that workspace. A licence is a signed record carrying the company, term and user limit; altering the file breaks its signature. You can follow its state later from the licence centre tab.
-
Invite the customer administrator
The third step sends an invitation to the administrator on the customer side. That person signs in to their own organisation area and defines their users and departments. End users get the narrow portal, where they see only their own requests and their own devices.
-
Place a thin collector if needed
If switches, firewalls and servers on the customer LAN need to be visible live, a small collector goes on site. Scanning runs locally and results travel one way, into that customer’s workspace. If endpoint inventory is in scope, the agent MSI is rolled out at the same stage.
-
The customer sees their inventory in their own area
Devices, warranty and licence dates, the network map and open requests accumulate in the customer’s own area, and their administrator pulls reports from there. This is where your service becomes visible: the work you do is tied to records and evidence.
-
You see only what was shared
When the customer wants to share inventory or a summary, they send it to you and you accept it in the sharing queue. Sharing is off by default. That protects the customer’s ownership of their data and keeps your operations area free of records you do not need.
Partnership application
Let us get to know each other first
Which firms fit this programme?
Firms already providing IT support, maintenance, network or systems services to customers. Conversations tend to be productive with companies that have their own technical team, go to customer sites, and are trying to run support work in one tool. Fit and scope are settled in a conversation after you apply.
Do I need a full installation for every customer?
No. The default path is opening a workspace for that customer from the Operations Centre, with a thin collector on site only when LAN visibility is required. If a customer deliberately wants the entire product on their own server, that is handled as a separate deployment.
Could one customer’s data become visible to another?
No. Each workspace is a separate data area, and access control is enforced in the API and query layer rather than in the interface. A customer’s inventory is also not copied into your operations area automatically; you see only the records the customer shared and you accepted.
How do the commercial terms work?
Pricing, licence model, partner terms and support scope are settled in a conversation after you apply. We deliberately publish no figures here, because the terms depend on the size of the firm, the target customer profile and the service model.
Can I join now and start selling tomorrow?
We would rather be clear up front: the programme moves in steps. The product is measured first inside our own field operation, then with a small number of customers we serve directly, and partner intake opens at the same pace. What the timeline looks like for your firm is settled in the conversation.
I already use another tool — why PolariStar?
We are not copying the feature lists of established products. PolariStar focuses on showing which customer a request belonged to, which device it touched, which change resolved it and who approved it, in one chain of records. A Turkish interface, the on-premise option and a local product team come with that. How it sits next to your current tool is best discussed with concrete examples.