PolariStar — İstar Bilişim Türkçe Request a demo
Technical operations platform for in-house IT teams

The ticket is closed. But what actually changed, and on which device?

Most systems show the request, the inventory and the network on separate screens. PolariStar keeps which user asked, which device it touched, what changed and who approved it in a single record. It runs on your own server, inside your own network.

Runs on your own server · Your data never leaves your network

PolariStar overview screen: open requests, SLA risk, device status and the priority queue on one screen
Ticket #0847 Accounting PC cannot reach the network Closed · 45 minutes
  1. 1Where it came fromPortal
    Accounting department
  2. 2Who reported itAyşe Yılmaz
    Accounting · 2nd floor
  3. 3Which deviceDESKTOP-ACCOUNTING
    On record in inventory
  4. 4Where on the networkSW-FLOOR3 · Port 14
    VLAN 20
  5. 5Who worked on itGökhan Dalda
    45 min logged
  6. 6What changedPort configuration
    before / after
  7. 7What the user sawResolution notice
    portal + email

All seven steps live in one record. Six months later, “who last touched this device, what did they change, and who approved it?” is not a search — it is a click.

When IT work lives in six different places

An IT service firm usually keeps tickets, inventory, topology, passwords, licences and quotes for the same customer in separate places. Nothing is lost; it is just that nobody can see all of it at once.

Scattered across tools

  • — You fix the same fault for the third time, with no record of the first two
  • — The ticket is closed, but which port changed was never written down
  • — A customer asks “what did you do?” and the report is typed by hand
  • — The server warranty expired last month and nobody noticed
  • — Passwords sit in a notebook, with no record of who opened it

In PolariStar

  • ✓ The device is entered once; tickets, tasks and reports attach to it
  • ✓ Configuration before and after stays on the record
  • ✓ The service summary is built from the logged work
  • ✓ Licence, support and warranty expiry become tasks at 90/30/7 days
  • ✓ The vault is encrypted; viewing and copying are audited

Two editions, one product

The same data model; the interface language changes with the workspace type. What a service provider calls a “customer” is a “department” inside a company.

PolariStar IT

For in-house IT teams running their own infrastructure. The language is built around departments, locations and users.

Core concept
Department, place, user
Inventory
One company inventory
Sales
None — renewal tracking only
Extra screen
Sharing with your provider

PolariStar MSP

For IT firms serving several customers. The firm runs its own internal work in the same workspace.

Core concept
Customer, contact, site
Inventory
Organisation + per customer
Sales
Catalogue, quotes, suppliers, commission
Extra screen
Operations Centre
MSP mode compared with organization modeA two-column comparison. On the PolariStar Op side the other party is a client, inventory is scoped per client, quotes and margin are visible, and there is an Operations Center. On the organization side the same concept is a department, inventory is one company's, there is no sales surface at all, and the mode's own screen is the one that sends records to Op. Both rest on the same data model.Two operating modes — one engine, different vocabularyPolariStar Op (MSP)A service provider with many clientsOrganization (IT)A company running the product for itselfThe other partyClientDepartmentRequest recordTickets / technical workRequestsInventoryA separate inventory scope per clientOne company inventory, organized by placeSalesQuotes, catalog, cost and marginNo sales surface at allIts own screenOperations Center — opening tenantsSend to PolariStar OpThe same data modelOne codebase, one schema, one client-contact-device context. Only the menu, the wording and the theme differ.

You decide where the data lives

PolariStar runs on your own server. Your data never leaves your network, and you decide what, if anything, is shared outside it.

Workspace

A data area is opened centrally without a full install at the customer. Users, requests and inventory live there.

Local collector

A small collector on the customer network scans read-only over SNMP. It never writes to devices and only makes outbound connections.

On your own server

A Docker-based on-premise package with a signed licence and encrypted backups, for companies that want the whole product in-house.

Sharing is your choice

Inventory ownership stays with the customer. The customer marks what goes to the provider; the provider accepts it.

How PolariStar is deployedA three-layer flow diagram. Devices at the customer site, plus a thin local collector, push data outbound only into the customer's own workspace. Inventory and the local network stay there. The service provider, PolariStar Op, sees only the records the customer chose to send and Op accepted. The flow runs one way.Deployment model — where the data rests, which way it flowsSITECustomer siteNetwork gear, servers, PCs and a thin local collector.The collector scans read-only and pushes into its own tenant.CUSTOMERThe customer's workspace (tenant)Inventory and the local network stay here, separated by tenant scope.The customer sees their own devices, requests and reports here.SERVICE PROVIDERPolariStar OpOp sees only records picked for sending, after an approval queue.End users never see this sharing menu.One direction: outbound connections onlyNo inbound port is opened to the site; the collector dials out.Only what has been accepted is shared1 pick a type → 2 add devices or text → 3 Op accepts.Customers do not get a full install: a tenant is opened from the Oppanel, and a thin collector goes on site only when local networkvisibility is needed. A fully offline package applies only if a customer wants the whole product on their own server.

From the interface

Screens are taken from the product demo environment; the data is sample data.

PolariStar overview screen with queue, open tickets, SLA risk and infrastructure cards
OverviewThe day's queue, SLA risk and infrastructure status on one screen.
Ticket list screen with status ring and filters
TicketsFilter by clicking the status ring; track time and resolution.
Network map screen with LLDP/CDP discovery and device counters
Network mapNeighbours discovered over LLDP/CDP, manual correction and location areas.
Support reports screen with report scope filters
ReportsSupport reports by customer, owner and date; Excel/CSV export.

See it on your own operation

Let us open a workspace for you and try it with your own customers and devices. We will guide you through setup and data migration.