About IPfonix, Inc.

We were incorporated in the year 2000 and remain a small, privately held software company located just outside of Boulder, Colorado.

We began work on our first KDC in November, 2000. It began initial bilateral interop testing with an MTA reference design vendor in December, 2000 and became available to customers in April, 2001.

Our goal has always been to produce, at the lowest possible price, the best possible Key Distribution Centers for PacketCable (and, latterly, CableHome) networks. Our KDCs are now in use around the world in development, testing and deployment networks.

We borrow our corporate philosphy from the Four-Way Test of Rotary International:

1. Is it the truth?
2. Is it fair to all concerned?
3. Will it build goodwill and better friendships?
4. Will it be beneficial to all concerned?

We attempt to apply this philosophy to all our relationships, whether with customers, OEM resellers or third parties. We believe that it is important to treat all customers as partners, so that we might share in each other's success as PacketCable technology becomes more widely deployed.

We also apply this policy to our pricing procedure. We are aware that there are few, if any, viable alternative KDCs that really conform to the published PacketCable specifications and which have been designed from the ground up to be secure against premeditated attack (to give just one example, attacks designed to overflow buffers are thwarted because our KDCs make no use of unprotected internal buffers). Even so, we price our KDCs at the lowest possible price; this encourages MSOs to deploy properly-secured PacketCable systems, which we believe is in the interest of both MSOs and their customers. We strongly believe that deploying insecure systems is a false economy that does a disservice to everyone involved. By pricing KDCs at a per-subscriber level that is as low as possible, we hope to encourage MSOs to deploy PacketCable in the manner that it was intended to be deployed, rather than in a manner that puts themselves and their subscribers at risk.

For more technical details about our products, please consult our FAQs.