Trust Center
Which vendor connections are live, which run against a simulator, and which are not open yet. Boostlete LLC operates VitalFax.
Not every vendor on the data path is connected yet
VitalFax is new and the table below says exactly where that is true. An integration marked Simulator runs finished code against a simulator — nothing reaches a real vendor, and nothing is recorded as though it had. An integration marked Not open refuses every request rather than failing quietly.
2 live · 5 on a simulator · 10 not open
Vendor connections
The same state the operator console reads, stated publicly.
Fax carriers
Fax simulator runs against a simulator. The code is finished; nothing reaches a real vendor, and nothing is recorded as though it had.
WestFax — carrier #1 is connected and carrying live traffic.
Concord — carrier #2 is built and waiting on a vendor account. It refuses every request until one exists rather than failing quietly.
Documo — carrier #3 is built and waiting on a vendor account. It refuses every request until one exists rather than failing quietly.
srfax — carrier is built and waiting on a vendor account. It refuses every request until one exists rather than failing quietly.
Database and storage
Document storage runs against a simulator. The code is finished; nothing reaches a real vendor, and nothing is recorded as though it had.
Database is connected and carrying live traffic.
Payments
Payment processing runs against a simulator. The code is finished; nothing reaches a real vendor, and nothing is recorded as though it had.
Email and SMS
Transactional email runs against a simulator. The code is finished; nothing reaches a real vendor, and nothing is recorded as though it had.
SMS notification runs against a simulator. The code is finished; nothing reaches a real vendor, and nothing is recorded as though it had.
Direct and FHIR
Direct Secure Messaging is built and waiting on a vendor account. It refuses every request until one exists rather than failing quietly.
FHIR is built and waiting on a vendor account. It refuses every request until one exists rather than failing quietly.
EHR connectors is built and waiting on a vendor account. It refuses every request until one exists rather than failing quietly.
Document intelligence
Document intelligence (OCR, classification) is built and waiting on a vendor account. It refuses every request until one exists rather than failing quietly.
Marketing channels
Social publishing is built and waiting on a vendor account. It refuses every request until one exists rather than failing quietly.
Podcast production has no implementation yet. It is a named slot, and it reports nothing as available.
Video production has no implementation yet. It is a named slot, and it reports nothing as available.
What VitalFax does not claim
The things a trust page is usually used to imply.
There is no HIPAA certification
No such certification exists for anybody. What exists is a documented set of controls, a Business Associate Agreement, and a register of subprocessors. Any vendor telling you they are “HIPAA certified” is describing something that is not a thing.
No SOC 2 report, and no audit yet
VitalFax has not been through a SOC 2 examination or an independent penetration test. Commissioning one is a recorded, outstanding task rather than something being quietly deferred — and until a report exists, there is nothing here that implies one does.
The agreements have not been reviewed by counsel yet
The Business Associate Agreement and the Terms of Service are drafted and are marked pending review on the pages that serve them. They are not presented as reviewed text, because they are not.
No reference customers with years of history
VitalFax is new. There is no customer list to point at and no case study with three years behind it. If that is what you need, this is not the right time to buy.
The detail
Each of these is its own page.
Tenant isolation, encryption, access control and the audit trail.
The HIPAA posture, the BAA, and the reports a customer can run.
Every third party that would handle customer data, and the agreement status with each.
Whether the connections above are healthy right now.
Something missing, or something here that does not match what you were told? Write to security@vitalfax.com.