From open source project to company
teemIP was not created from an empty product brief. The software has existed since 2011 and has grown through real network operations, community feedback and the needs of organizations that wanted an IPAM repository they could understand, host and adapt.
The creation of teemIP SAS gives that technical base a professional frame: support, integration, training, project assistance and a readable product roadmap. The goal is not to replace the community model, but to make adoption easier for teams that need commitments and continuity.
Addressing an invisible network debt
In many organizations, IP addresses, DNS zones, DHCP ranges and CMDB relationships are still documented in spreadsheets, local scripts or individual memory. This works for a small perimeter, then becomes fragile as soon as several sites, teams and thousands of addresses are involved.
The debt is often invisible until an incident, an audit or a migration exposes it. Duplicate addresses, unknown owners, forgotten subnets and unclear dependencies slow projects down and reduce confidence in network data.
IPAM, DDI and CMDB in the same trajectory
teemIP is built around a simple idea: an IP address has operational value only when it can be connected to a device, a service, a site, an organization, a DNS record, a DHCP reservation or a change request.
This is why the project combines IPAM, DDI documentation and CMDB integration, especially around iTop. The objective is to turn addressing data into a shared operational repository rather than another isolated inventory.
A sovereign and open source answer
Open source matters because network governance should not be a black box. The code can be inspected, the installation can remain under the customer's control, and the data model can be adapted to real constraints without locking the organization into a closed appliance model.
For sensitive environments, this reversibility is not theoretical. It supports internal security reviews, on-premise deployment, long-term maintainability and a clearer relationship between the customer, integrators and the editor.
A founding team rooted in field experience
The company is carried by complementary profiles: commercial development and partnerships, product vision and historical expertise around teemIP, plus integration and customer delivery around real ITSM and CMDB projects.
That balance is important. IPAM projects are rarely only technical. They involve data quality, ownership, operating models, documentation habits, budget decisions and change management across several teams.
What comes next
The next step is to structure professional offers, strengthen the partner ecosystem and support early customers while keeping the open source base visible and useful.
The ambition is pragmatic: make teemIP a serious European open source reference for IPAM/DDI governance, with a product path that remains understandable for network teams and decision makers.
Want to explore teemIP?
Download the open source version directly.