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 server. 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 fosters interoperability with other Kipu clients (so you can transfer clients between facilities who use Kipu) and for communications with labs, salesforce, other CRMs, Kipu Marketplace add-ins like VOBGetter, and 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.
A single Kipu instance can support multiple program tracks as well as multiple physical locations or buildings making up part of an agency or facility. A Kipu Master Instance can tie together all sub-instances for login to all facilities by administrators with single facility login for staff.
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.