Hey Todd, Unfortunately there are no simple options for redundancy right now. However, we're getting very close to finishing our new [cluster packages](http://gluu.org/docs-cluster). They should be ready for public consumption within the next 2-3 months. We're configuring these for some of our supported customers right now, but its still early days. Basically I think you have two options right now: 1) We can discuss a support contract that includes setting up clusters for your org now, or.. 2) Wait until the packages are complete and ready for the public. One thing to note regarding clusters... we always do at least one clustered development environment and one clustered production environment. So typically four servers at a minimum. Sometimes large customers also have a QA cluster environment. Hope that helps. Feel free to [schedule a meeting with us](http://gluu.org/booking) if you want to discuss further. Thanks, Will

Ok. But as far as having two hosts. Why couldn't both hosts have the same metadata and couldn't you just point the standby host via DNS if the primary one fails? I'm just trying to think of temporary options.

Hi Todd, >> Why couldn't both hosts have the same metadata and couldn't you just point the standby host via DNS if the primary one fails? That won't support failover IDP cluster purpose. Our cluster solution includes File system replication, LDAP replication, session management etc. This way an user won't even understand if server goes down because his/her session and ldap data will active even after the outage of any node.