Where Is Teller Hosted, and How Reliable Is It?

‍

Teller is hosted on Amazon Web Services, with the primary region in Oregon and a disaster-recovery region in Virginia. Because it is cloud-hosted, jurisdictions do not run Teller on their own servers or maintain on-premise infrastructure for it. Our service is backed by a 99.9% availability SLA during business hours that includes financial remedies for downtime, giving state and local governments enforceable commitments rather than best-effort statements. Further, as part of our commitment to security and reliability, Teller undergoes an annual SOC 2 Type 2 audit and encrypts data at rest and in transit.

‍

‍

What happens if an AWS region fails?

‍

Teller's disaster-recovery design is defined by two figures for a full-region failure:

‍

• Recovery Point Objective (RPO): 5 minutes. In the event of a full-region failure, no more than five minutes of data would be at risk.
• Recovery Time Objective (RTO): 1 business day. Service is targeted to be restored within one business day of a full-region failure.

‍

The Virginia disaster-recovery region exists to support this recovery posture if the Oregon primary region becomes unavailable.

‍

‍

How does Teller secure and control access to data?

‍

• Encryption. Data is encrypted at rest and in transit. Key management uses AWS KMS (Key Management Service).
• Independent audit. Teller undergoes an annual SOC 2 Type 2 audit, an examination of controls over a sustained period rather than a single point in time.
• Authentication and SSO. Teller authenticates through OpenID Connect (OIDC) and supports single sign-on via Microsoft Azure AD and ADFS, so agencies can manage Teller access through their existing identity provider.

‍

For the full certification picture, see What security certifications does Teller have?. For how Teller connects to your existing systems, see Integrated by Design.