BAM has always been one of the components of Integrity. BlueCat Integrity consists of two things as part of BlueCat’s DDI Management Platform offering. BlueCat Integrity = BlueCat Address Manager (BAM) + BlueCat DNS and DHCP Server(s) (BDDS). The BAM UI and RESTful API provides full visibility and control over any BDDS deployed.

So, we are using  BlueCat Address Manager (BAM) and DHCP Server(s) (BDDS)at ver 9.6.1, but not BlueCat DNS.

Would a future upgrade move us into “Integrity”?

A single BDDS can handle both DNS and DHCP functions. However, there may be specific reasons in your deployment with BlueCat for using only DHCP. As a best practice in the industry, it is advisable to separate the roles by having one server manage DNS while another handles DHCP. Both BDDS appliances/VMs and their deployment roles will be managed by BlueCat Address Manager (BAM).

Integrity is the BC product name for the BAM/BDDS combo that was previously Proteus/Adonis. It is the Foundation that the BC line of products was built on.

You can see the Proteus and Adonis names in the admin console in the latest versions.  It’s probably low priority to change those to BAM> and BDDS>.

Integrity is the product name for our enterprise DDI solution, originally known as Proteus and Adonis, the solution is made up of various functional components

• BlueCat Address Manager (BAM) is the centralised IPAM (control plane)
• BlueCat DNS/DHCP Services (BDDS) are the DNS/DHCP services node
• BlueCat Gateway is an optional but f.o.c python SDK
• BAM and BDDS appliances can be dedicated hardware, or virtual/cloud based appliances

​@allen.watson you already have Integrity, you are running Integrity 9.6.1, which is the latest product until Integrity X 25.1 launches this summer