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

Construire et intégrer le logiciel de localisation dans vos systèmes of record.

Stratégie et delivery comme une équipe — normalisation d’événements vers WMS, ERP, MES ou EMR. Code source à vous.

Indépendance : TRACIO ne possède, ne licence et ne revend pas de plateforme de localisation. Le platform build, c’est l’architecture et la livraison de votre logiciel — la propriété du code vous est transférée. Nous ne prenons aucune marge revendeur sur la stack sous-jacente.

Quand ce service convient.

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.

Comment nous travaillons.

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 technologique recommandé.

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.

Ce que vous obtenez.

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’indépendance s’applique aussi ici.

Nous ne vendons pas de matériel, ne touchons pas de commissions revendeur et n’avons aucune relation commerciale avec les fournisseurs GPS, télématique, RFID, BI, cloud, identité ou fleet management recommandés dans une architecture. La sélection finale se fait en discovery sur le fit opérationnel — pas au stade de la proposition sous biais commercial.

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

Questions fréquentes

Construisez-vous la plateforme vous-mêmes ou avec des partenaires ?

Les deux — architecture et livraison sont de notre ressort ; pour les métiers spécialisés nous faisons appel à des partenaires éprouvés. Une seule équipe reste accountable face au client.

Quels types de plateformes avez-vous livrés ?

Des plateformes de localisation, d’identité et d’opérations pour RTLS, RFID et IoT adjacent — avec intégrations MES, WMS, ERP et ITSM.

La plateforme peut-elle être construite en open source ?

Oui, quand le fit est bon. Nous ne choisissons pas l’open source par idéologie, mais quand maintenabilité, licence et compétences collent à l’organisation.

Comment protégez-vous le client sur un forfait fixe ?

Périmètre clair, contrôle des changements et jalons visibles. Un forfait sans discipline de scope n’est qu’un conflit différé — nous l’évitons.

Et si nous voulons une stack différente de vos recommandations ?

Nous documentons les arbitrages et construisons la stack choisie — tant qu’elle porte les contraintes et l’adéquation au référentiel.

Transférez-vous le code source et la PI ?

Oui. Le client possède le code livré et la PI convenue. Nous ne vendons pas une plateforme produit à louer.

Conseillez-vous plutôt que de construire si c’est la meilleure réponse ?

Oui. L’indépendance, c’est aussi refuser un build quand acheter, configurer ou ne rien faire est préférable.

Ready to scope it?

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

Réserver un appel de cadrage de 30 minutes

Last updated: