Telecom-native
Designed around location, supplier, product, contract, quote, order, and delivery realities.
About Trunkstar
Telecom-native software for the work between supplier and customer
Trunkstar is a telecom software company with teams in Amsterdam, Madrid, and São Paulo. The company builds configurable connectivity lifecycle environments for carriers, ISPs, MSPs, VNOs, and wholesale providers.
Our focus
Give connectivity teams more time for valuable decisions
Trunkstar focuses on a recurring operational problem: experienced telecom teams can spend substantial time repeating searches, moving data between tools, reconstructing quotes, and chasing workflow context that software can organize more effectively.
The company focuses on the commercial and operational lifecycle between customer demand and delivered connectivity, with automation for repeatable work and visible human handling for exceptions.
How we build
Configurable by design
Every provider has its own supplier relationships, products, commercial model, terminology, customer journey, and existing systems. Trunkstar supplies modular building blocks and an API-first integration model instead of requiring every provider to operate the same way.
The result can be an internal workflow, a provider-branded customer environment, or a combination of both.
Operationally practical
Automate repeatable steps while keeping firm supplier responses and exceptions visible.
Provider-controlled
Keep the provider's proposition, relationships, commercial rules, and customer experience central.
API-first
Connect lifecycle workflows with CRM, customer portals, and other business systems.
Where to find us
Amsterdam, Madrid, and São Paulo
Trunkstar works from Amsterdam in the Netherlands, Madrid in Spain, and São Paulo in Brazil. These locations give the team local-time-zone coverage for customers, partners, and supplier ecosystems across Europe and the Americas.
Working together
Begin with the workflow that matters
A useful first conversation maps the current supplier sources, users, handovers, commercial rules, exceptions, and systems. From there, the team can demonstrate the relevant Trunkstar modules with a clearer view of the problem to solve.
Keep exploring