Master Instance

Kipu Cloud Network Topology

Guaranteed 99.99% Availability

This network is replicated hundreds of times in data centers throughout the United States.

Instances, Locations & Master Instances


Each client facility runs its own unique installation of the Kipu software on a redundant set of servers in Kipu’s hosted cloud network.

A typical client installation includes a redundant set of up to 24 application servers (the larger the client, the more servers are allotted. It’s actually unlimited!), several redundant database servers, and a background task server. (Illustrated below)

Those servers are backed up in what is called a “Redundant and Mirrored” backup in another data center in another part of the country. If your primary servers should fail for any reason, whether it be hardware or natural disaster, then your processing is automatically redirected to the next available servers, and your instance continues to operate.

There is a fifth virtual server assigned to your instance called a “Background Task Worker”. This server performs processing tasks and interoperability with other Kipu clients (so you can transfer clients between facilities who use Kipu) and for communication with labs, Salesforce™, other CRMs, Kipu Marketplace add-ins like VOBGetter, and finally for printing or creating large PDF case files. Example: A 500-page PDF could require 10-20 minutes to create. You are not sitting waiting at your PC for the creation of this large file. Rather, that task is worked off by the background task server so you can continue working, then pick up that PDF file when it’s ready.

Your system performance is monitored in real time, and Kipu automatically scales server size and allocated bandwidth as your census and use of the system increases. Kipu is ultimately scalable to an unlimited size per instance.


The “Programs” feature is completely customizable and allows the facility to separate or segregate patients by programs or tracks that they may be assigned. This is optional, your implementation may have two “programs” like PHP and IOP, or Detox and Treatment, or you could have a more complex setup as shown here. The choices are almost unlimited.

The “Programs” feature is managed within the Locations feature so that each “location” can drill down into programs.




Your instance also has the ability to have multiple (almost unlimited) locations. A location is best defined as another location or building. It could be different residential facilities, or different treatment facilities. “Locations” work within an agency using the same chart across all locations. For example, Recovery Right Meow™ has three different addresses where they operate Recovery Right Meow™ facilities. They could be all IOP, or they could be PHP in one, IOP in another and OP in the third. That client would set up three locations which operate in the same instance. Staff is assigned to one, two, or three locations at login. With this feature, staff at one facility can see patients at other facilities. Master Instances are used where total segregation is needed.

Single Instance Topology

This illustration represents a rough visual representation of what the Kipu cloud network might look like. With a single instance or client facility implementation might be better (and roughly) represented by this (virtual) server topology.

Master Instance

Any client running multiple Kipu EMR instances can elect to have a Master Instance created to act as an umbrella over all Kipu instances or facilities.

A Master Instance allows multiple KIPU facilities (instances) to operate with “walls” between them, yet transparently as a single “Master Instance” so that all user control, accounting, admission, VOB, UR, Clinical Review, etc. can be consolidated into a single sign-in for all the facilities you operate. No more logging in and out of various facilities.

Each facility continues to function as a single instance, where client data is segregated from other facilities by what we call “walls.” Logins can be set to one or many facilities within the Master Instance.

“Examples” of Master Instances:

  • For example, a staff member in Facility “A” can be set up to log into and see patients only in Facility “A.” Same for Facility “B.” However, a Clinical Director can see all patients in BOTH Facility “A” and Facility “B” if you create the login that way. Each login can be set to one or many instances, individually.
  • An agency with ten Eating Disorder and ten Drug Treatment facilities could select a single Master Instance covering all facilities (Instances) or could select one Master Instance for all Eating Disorder and One Master Instance for Drug Treatment Facilities.
  • Likewise, one Kipu Client with six Detox facilities throughout South Florida and New Jersey and 3 IOP facilities in New Jersey may select two Master instances; one for the six Detox facilities and one for the three IOP facilities.
  • Your Client Services or Kipu Sales Consultant can elaborate and assist you in selecting what is right for you.

For Commercial Biller and Labs

A variation of this feature, using Kipu Single Sign-On, is also available for commercial billers, labs and other third parties who continually log into multiple instances. Third parties can now log into multiple instances with a single set of credentials, and a single login. All instances allowed under the consolidated login feature will remain open and available to the biller/lab without having to log into multiple instances, and without having to share logins. This is also a requirement for maintaining Kipu Gold Certified Biller Accreditation.

Locations and Instances Q&A

How Much Do Locations Cost?

Locations are included*. You may have as many as you want. Example: we have one large client with one instance and seven locations (they pay for only one instance). We have another client with six different “locations” in one instance, again, they pay for only one instance. Yet another client runs five instances under different names and 35 locations. Finally, we have a client with 13 instances, one per location, because each one has different owners and needs to be completely separate. The possibilities are endless.

How Am I Invoiced When I Have Multiple Locations?

We generate one monthly invoice per instance. If you require separate invoices, you will need separate instances.

When Do I Need A New Instance?

Clients who have different locations or facilities where:

  • There is separate ownership, or facility names where different systems are required by your legal or compliance team; or…
  • There is a requirement of different invoices generated for each facility; or…
  • The facilities are In-Network and Out-Of-Network, and compliance or legal requires absolute separation of the two; or…
  • The facilities are in different time zones (this will be improved in future updates).

How Am I Invoiced When I Request Additional or Multiple Instances?

New Instances using the same chart require new virtual servers, licenses, and implementation, and are billed at 50% of the price published on the most recent Kipu price list. You can also get separate invoices, and there is a $500 maintenance fee, per instance, to cover the cost of the additional servers and licenses we must pay for.

Can A Master Instance Eliminate The Need For New Instances and Their Cost?

A Master Instance simply consolidates all of your instances together, so that management access all facilities with a single login. You still need to license a new instance for each new facility.

*Some exceptions apply; see first page of your agreement