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

Construir e integrar software de localização nos systems of record.

Estratégia e delivery como uma equipa — normalização de eventos para WMS, ERP, MES ou EMR. Código-fonte para si.

Independência: A TRACIO não possui, licencia nem revende uma plataforma de localização. Platform build significa arquitetura e entrega do vosso software — a propriedade do código transfere-se para vós. Não cobramos margem de reseller no stack por baixo.

Quando este serviço encaixa.

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.

Como trabalhamos.

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 tecnológico recomendado.

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.

O que obtém.

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.

A independência também se aplica aqui.

Não vendemos hardware, não recebemos comissões de reseller e não temos relações comerciais com os vendors de GPS, telemática, RFID, BI, cloud, identidade ou gestão de frotas recomendados em qualquer arquitetura. A seleção final acontece no discovery por encaixe operacional — não na proposta por viés comercial.

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

Perguntas frequentes

Constroem a plataforma vocês ou com partners?

Ambos — arquitetura e entrega são nossas; para ofícios especializados trazemos partners comprovados. Uma equipa permanece accountable perante o cliente.

Que tipos de plataformas já entregaram?

Plataformas de localização, identidade e operações para RTLS, RFID e IoT adjacente — com integrações a MES, WMS, ERP e ITSM.

A plataforma pode ser construída em open source?

Sim, quando o encaixe é certo. Não escolhemos open source por ideologia, mas quando manutenibilidade, licença e skills combinam com a organização.

Como protegem o cliente num fixed-price?

Limites de âmbito claros, controlo de alterações e marcos visíveis. Fixed price sem disciplina de scope só adia o conflito — evitamos isso.

E se quisermos um stack diferente do recomendado?

Documentamos os trade-offs e construímos o stack escolhido — desde que suporte as restrições e o encaixe com o sistema de registo.

Transferem o código-fonte e a IP?

Sim. O cliente possui o código entregue e a IP acordada. Não vendemos uma plataforma de produto para alugar.

Aconselham em vez de construir se essa for a melhor resposta?

Sim. Independência também é recusar um build quando comprar, configurar ou não fazer projeto é melhor.

Ready to scope it?

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

Agendar uma chamada de scoping de 30 minutos

Last updated: