Service requests and projects in one platform, hosted in the EU.
ukulabs brings a full service desk together with agile project management and test management, on an open-source core. Your data stays in the EU and there is no per-user licence cost.
The entire interface is available in Lithuanian, Estonian and English.
Audio desk fault in Studio 4
Why organisations choose ukulabs
Built for public-sector organisations, media and broadcasting companies, and mid-sized businesses across the Baltics and the Nordics that want European data residency, predictable pricing and an alternative to Jira and Jira Service Management.
-
Your data stays in the EU
The service runs in Google Cloud europe-north1 in Finland. Records stay inside the EU and EEA, and you can export them in open formats whenever you want.
-
An open-source core you can read
The platform is built on GLPI 11, published under the GNU GPL v3. Nothing about your requests, assets or projects is locked inside a format only we can open.
-
No per-user licence cost
Adding a colleague to the service desk is not a budget decision. The open-source core carries no per-user licence cost.
-
Lithuanian and Estonian throughout
The full interface is translated, not only the login screen. People work in the same language they raise their requests in.
-
A way out of Jira
A migration toolkit brings you across from Jira Cloud, so changing platform does not mean leaving your history behind on the old one.
-
One system, not five
Requests, assets, changes, projects, sprints and test runs sit in the same database, so a fault and the change that caused it are one click apart.
Ten areas, one system
ukulabs Core runs underneath all ten: workflow automation, SLA escalation, security levels, a protected audit trail and reporting.
-
Service desk
Requests sorted by category, with SLA and OLA targets, and escalation from ukulabs Core when a target is at risk.
-
Forms and service catalogue
Request forms with conditional logic, a published service catalogue, and a knowledge base your agents write as they work.
-
Assets, licences and CMDB
Hardware, software and licences in one register, with configuration items, their relationships and impact analysis before anything is touched.
-
Change management
Changes planned and placed on a shared calendar, so two teams do not book the same maintenance window.
-
Projects
Gantt and Kanban views over the same plan, with dashboards that show where the work actually stands.
-
Agile
added by ukulabsBacklog, sprints, burndown and velocity, plus roadmap, portfolio, capacity and risk views for the people planning across teams.
-
QA and test management
added by ukulabsTest cases, test plans and executions, traceability back to requirements, and JUnit results imported from your build pipeline.
-
Studio orders
added by ukulabsOrders for studio and event services, from the first request through to a PDF confirmation.
-
AI assistant
added by ukulabsOptional and off by default. It is switched on centrally, every use is audited, and your data is never used to train models.
-
Identity and integrations
added by ukulabsSingle sign-on with Microsoft Entra ID, LDAPS directory sync, a REST API, webhooks, and the migration toolkit for Jira Cloud.
The areas marked added by ukulabs are our own modules. The rest come from the open-source core.
How it is delivered
ukulabs is delivered as software as a service from EU cloud infrastructure. There is no server for you to buy, patch or watch overnight, and no hardware to write into next year’s budget.
Everything in the table describes the service as it runs today. If your procurement team needs these points in a tender response, we will supply them in writing.
| Delivery | Software as a service |
|---|---|
| Cloud region | Google Cloud europe-north1, Finland |
| Data residency | EU and EEA |
| Backups | Daily, encrypted |
| Recovery point objective | 24 hours |
| Recovery time objective | 8 hours |
| Transport security | TLS |
| Idle session logout | 15 minutes |
| Audit log | 90 days, protected against change |
| Penetration test | Once a year |
| Data export | Open formats, at any time |
| Licensing | Open-source core, no per-user licence cost |
| Interface languages | Lithuanian, Estonian, English |
Built on GLPI 11
The core of ukulabs is GLPI 11, a mature open-source platform for service and asset management, published under the GNU GPL v3. We did not rewrite it and we do not hide it. The ticket engine, the asset register and the CMDB you work in are the open-source ones, and they stay open.
From the open-source core
- The ticket and request workflow engine
- Asset and licence register
- CMDB and configuration item relationships
- Change management
- Knowledge base
- Projects
Added by ukulabs
- Core: workflow automation, SLA escalation, security levels, audit and reports
- Agile: backlog, sprints, burndown, velocity, roadmap, portfolio, capacity, risks
- QA: test cases, plans, executions, traceability, JUnit import
- Studio orders with PDF confirmations
- AI assistant, optional and off by default
- Entra ID single sign-on and LDAPS sync
- Migration toolkit for Jira Cloud
GLPI is developed by its own community and distributed under the GNU GPL v3. ukulabs is a separate product built on top of it and speaks only for itself.
Sixty Four OÜ
ukulabs is built by Sixty Four OÜ, a software development and consulting company in Tallinn, founded in 2012. We write the modules, run the service and answer the phone ourselves.
- Address
- Kolde pst 23, 10412 Tallinn, Estonia
- Registry code
- 12354921
- VAT number
- EE102943256
- henrik.aavik@sixtyfour.ee
- Phone
- +372 509 2839
- Field
- Computer programming and consulting
See it working
Write to us and we will walk through the platform with your own scenarios in front of us. Tell us which language your team works in and what you use today.