Frequently asked questions
Straight answers on security, encryption, and how BinaryCord works.
What is BinaryCord?
BinaryCord is a hardened, observable infrastructure platform for engineering teams. It's built on zero-trust principles — every request is authenticated and authorized, whether it comes from outside your network or from another service inside it.
Is my data encrypted?
Yes. All data in transit is encrypted with TLS 1.3, and all data at rest is encrypted with AES-256. Encryption keys are managed separately from the data they protect, so a leaked storage credential alone is never enough to read your data.
What is zero-trust architecture?
Zero-trust architecture is a security model where no request is trusted by default, even from inside the network. Every request must be verified and authorized on its own merits — network location alone grants nothing.
Can I self-host BinaryCord?
BinaryCord is offered as a managed platform today. Self-hosted deployment is on our roadmap for teams with strict data-residency requirements — reach out on the contact page if that's a hard requirement for you.
How is BinaryCord different from a standard cloud firewall?
A firewall filters traffic at the network perimeter and generally trusts anything already inside it. BinaryCord verifies every request individually, regardless of where it originates, so a breach in one service can't silently move laterally to the rest of your infrastructure.
How do I get support?
Use the contact form to reach the team directly — messages are answered by an engineer, not a support script, typically within one business day.
