Consulting Independent advice across RTLS, RFID and IoT — no platform to sell. Book a call →
SERVICE · INDEPENDENT

Costruire e integrare software di localizzazione nei sistemi of record.

Strategia e delivery come un team — normalizzazione eventi verso WMS, ERP, MES o EMR. Codice sorgente a voi.

Indipendenza: TRACIO non possiede, non licenzia e non rivende una piattaforma di localizzazione. Platform build significa architettura e delivery del vostro software — la proprietà del codice passa a voi. Non prendiamo margine da reseller sullo stack sottostante.

Quando questo servizio è adatto.

Greenfield builds where no incumbent system exists — fleet management, asset accountability, EAM, maintenance management, location intelligence, IoT platform, vendor-neutral integration layer.

Legacy replacements where the operational requirements are well understood but the technology stack needs to change. Common drivers: vendor end-of-life, sovereignty mandate, scalability ceiling, integration cost spiral.

Multi-region rollouts where the platform has to work across time zones, languages, connectivity environments, regional workflows and political accountability lines.

Integration-heavy programmes where the value is in connecting GPS, telematics, RFID, RTLS, maintenance, fuel, ERP, HR, finance and audit systems into one operational platform — and no single vendor has the full stack.

Public-sector and audit-grade environments where source-code ownership, procurement compliance, data sovereignty and full audit trails are non-negotiable.

Startups and scale-ups needing a vendor-neutral, independently-architected platform without locking into a single SaaS provider's commercial model.

Come lavoriamo.

Discovery (fixed price). Requirements documentation, technical architecture, database design, API specification, security and audit model, integration architecture, UI wireframes for every module, signed-off project plan. End of discovery is a sign-off gate before any build commitment. Typical duration: 3–6 weeks depending on scope.

Build (milestone-priced). Sprints with bi-weekly client demos. Major milestones cover platform core, integrations, mobile, reporting and UAT. Each milestone has fixed deliverables, written acceptance criteria, a 5-business-day acceptance window and a defined payment trigger. Scope locks at discovery sign-off; later changes go through a written change request with separately quoted impact.

Go-live and warranty. Training (role-based), complete user and operations documentation, production deployment, source-code transfer and a 90-day post-go-live warranty during which defects are fixed at no charge. Continuous improvement and managed services are available as a separate engagement after warranty closes.

Stack tecnologico consigliato.

Backend — .NET 8 (C#) on Linux containers. Strong public-sector procurement story, mature tooling, long-term support. Node.js, Java Spring Boot or Go are also available where the client team's skills or existing systems make them the better fit.

Database — PostgreSQL 16 with PostGIS for geographic queries. Open source, no per-core licensing. SQL Server or MySQL where existing systems require it.

Web portal — Next.js (React, server-side rendered). Fast, SEO-friendly admin UX. Angular or Vue where the client engineering team's skills make them the better fit.

Mobile — Flutter — single codebase for Android tablet and phone, strongest offline-first architecture for field workforces. React Native or native Kotlin where requirements specifically demand it.

Cloud — Azure (including sovereign cloud where required) or AWS. Hybrid and on-premise deployments available for sovereignty-constrained environments.

GIS — Mapbox GL primary, OpenStreetMap fallback for cost-controlled high-volume use. Google Maps where existing licences exist or specific features are required.

Identity — Microsoft Entra ID + MFA, RBAC at the model layer with full audit logging. Okta, Auth0 or Keycloak as alternatives.

Reporting — Power BI Embedded for executive dashboards. Metabase or Apache Superset where open-source BI is preferred.

Cosa ottenete.

Full source-code ownership transferred on final payment. No per-seat licensing passed through. No vendor lock-in.

Complete documentation — technical, user, API (OpenAPI 3.0), deployment, operations runbook, disaster recovery procedures.

Role-based training for administrators, managers, operators and maintenance personnel. Train-the-trainer for the client's internal lead.

90-day post-go-live warranty. Defects fixed at no charge during the warranty window.

Ongoing options. Managed services, continuous improvement, expansion phases and feature releases available as separate engagements after warranty. Equally happy to hand over and walk away if that is what the client prefers.

L’indipendenza vale anche qui.

Non vendiamo hardware, non prendiamo commissioni da reseller e non abbiamo rapporti commerciali con i vendor GPS, telematica, RFID, BI, cloud, identity o fleet management raccomandati in alcuna architettura. La selezione finale avviene in discovery sul fit operativo — non in proposta per bias commerciale.

Where a custom-built platform is not the right answer, we say so. Where integrating two existing commercial products is cheaper and faster, we recommend that instead. The model is built around delivering the right outcome, not the most billable hours.

FAQ

Domande frequenti

Costruite la piattaforma voi o con partner?

Entrambi: architettura e delivery sono nostre; per mestieri specializzati usiamo partner collaudati. Un team resta accountable verso il cliente.

Che tipi di piattaforme avete consegnato?

Piattaforme di localizzazione, identità e operations per RTLS, RFID e IoT adiacente — con integrazioni verso MES, WMS, ERP e ITSM.

Si può costruire su open source?

Sì, quando il fit è giusto. Non scegliamo open source per ideologia, ma quando manutenibilità, licenza e skill combaciano con l’organizzazione.

Come proteggete il cliente in un fixed-price?

Confini di scope chiari, change control e milestone visibili. Fixed price senza disciplina di scope è solo una lite rimandata — la evitiamo.

E se vogliamo uno stack diverso da quello consigliato?

Documentiamo i trade-off e costruiamo lo stack scelto — purché regga i vincoli e il fit col system of record.

Trasferite codice sorgente e IP?

Sì. Il cliente possiede il codice consegnato e l’IP concordata. Non vendiamo una piattaforma prodotto in affitto.

Consigliate invece di costruire se è la risposta migliore?

Sì. Indipendenza significa anche rifiutare un build quando comprare, configurare o non fare progetto è meglio.

Ready to scope it?

30 minutes on the use case, the technology and the numbers.

Prenota una call di scoping di 30 minuti

Last updated: