We connect to the world

Some technical aspects of our solution

Because our application is built with Knack, Twilio, Zapier and Webmerge, we can rely on scalability and security:

​Encryption in transit - We encrypt all data as it moves between our servers and your web browser.Our API is fully encrypted so every request to view or update your records automatically encrypts that data behind the scenes.Encryption at rest - We encrypt all data that's stored on our servers.This includes both the records stored in our databases and search indexes as well as any files and images you've uploaded to your Knack database.Bank-level Encryption - We use both SHA-256 and AES-256 encryption, the strongest encryption available.This is the same level of encryption that banks use.

InfrastructureAmazon's secure data centers enable the redundancy and scaling that equates to a secure and reliable service for your database

Built in Redundancy - Knack uses AWS features like Auto-Scaling and Elastic Load Balancing to ensure that our production systems remain online and traffic is always routed to healthy instances.We continuously replicate your data and have it ready to bring online if any primary nodes fail.Compliance - AWS environments are continuously audited, with certifications from accreditation bodies across geographies and verticals.Amazon has achieved compliance with the most strict compliance programs.

DDoS Mitigation - AWS provides a robust platform that is not only pre-built to mitigate some attacks, but it also allows us to react quickly to spread out impact if there is an attack.We've also added safeguards to underlying servers as an additional level of protection.

​Offline Backups - we store physical backup files in a separate location from the servers as a final safeguard in case of major catastrophe.These backups are made on a daily basis and are encrypted using AES-256 encryption keys.

Multiple Databases - We mitigate database failures by storing your data in multiple databases, so if one database goes down the other databases can pick up the slack.Each change made to your database immediately propogates to these redundant versions.