See where every ticket and asset actually is
.png)

across Poland and CEE





Built for teams whose assets aren't all in one building
Everything a location-based team needs

Map-Based Ticket & Asset View

Assets Tracked by Where They Actually Are

Field Operations Beyond IT

Field Staff Report Issues From the Site

Multi-Language Interface
From first conversation to system live — without the guesswork
We learn your process

We configure your instance

Your team goes live

Watch how Mint actually works.
See exactly what's included at each level
Questions we hear most often
It depends on the deployment model and configuration scope. Cloud and Managed setups are typically faster to launch. On-Premises requires installation on your own infrastructure. Integration scope, SLA configuration, and data migration from a previous system are usually what determine the timeline.
Yes. Mint supports data migration from most common ITSM systems. The exact scope and method (CSV import, API) are defined during implementation. In practice, migrating historical tickets is rarely a hard requirement for going live.
Correct — Mint's AI module runs locally on your infrastructure (On-Premises and Managed deployments). Ticket data and AI-processed content are never transmitted to external cloud models. It's available as a paid add-on.
Yes, we offer a 14-day trial period that allows you to test Mint SD Cloud, so you can see how our solution meets your business needs before making a purchase.
Location data comes from the ticket or asset record itself — entered manually, imported via CSV, or synced through integrations like baramundi and Lansweeper, depending on your setup.






