What you need to assess SynapseTel Cloud

Legal name

SYNAPSETEL CLOUD LLC

Registration number

L26000459009

Jurisdiction

Florida, United States

Public registry

Florida Division of Corporations record

Registered address

Provided in the MSA or statement of work.

Contracts are signed with the registered Florida limited liability company below. The registration can be checked in the public registry. The business address is stated in the MSA or statement of work rather than published here.

Three options are published. The Assessment Sprint is a fixed fee of $14,500 for ten business days, starting once the read-only access checklist is complete; the full fee is credited on the first annual invoice of an Annual Platform Retainer or annual Managed Orchestration agreement signed within 30 calendar days of the read-out. The Platform Retainer is $24,000 per month, invoiced monthly and cancellable or pausable at the end of any billing month with 30 days’ written notice and no exit penalty, or an annual amount stated on the pricing page. Managed Orchestration is quoted per estate; its base tier covers up to 2 production OpenShift clusters and 1 regional Ericsson ENM or VMware vSAN estate.

Purchase orders, negotiated MSAs, agreed net terms and ACH or wire payment are supported. Cloud usage, licences and third-party fees are always separate from our fees.

See pricing and plan details

Systems, deliverables, engineering capacity, support hours and acceptance criteria are agreed in writing before work begins. Additional work needs an agreed scope and price: each scope is quoted as a versioned document in the client portal and approved before it is invoiced.

Production changes follow the same path: a written method of procedure, a merge request in your repository, your CI and policy gates, and an approval record from your change authority before execution.

Each engagement names what we need from you. The usual list:

• Named owners for the platforms, applications and infrastructure in scope, and a decision maker who can approve or stop a change
• Read-only access first, through your bastion or ZTNA gateway, with named accounts; write access only for approved steps in an agreed window
• Vendor subscriptions, licences and support entitlements for the products in scope
• Repositories and CI pipelines where our work is committed and reviewed
• Availability of your engineers during discovery, rehearsals and maintenance windows
• Confirmation of who validates each workload and its data recovery

We do not take custody of production data. Work happens inside your networks, bastions and repositories; production configurations, diagnostics and secrets stay in your systems. Findings we carry out of the estate are sanitised.

Code, manifests, diagrams, runbooks and validation evidence are committed to your repositories and belong to you at every milestone. The website and client portal process contact, account, service and billing records only; the privacy notice describes that handling.

Read the security and operational policy

Acceptance criteria are written per service in the statement of work and checked against recorded evidence: representative workload, interface and recovery checks, with results stored in your repository. Acceptance is your decision against those criteria; open conditions stay visible until closed.

Every stage ends with the work committed in your repositories. Cutovers run with your operations team, runbook handover sessions are recorded, and ongoing support continues only under a separate retainer or managed agreement.

See the delivery standards and sample records

Response targets are distinct from restoration or availability guarantees.

• Normal support: Monday to Friday, 8 a.m. to 6 p.m. Eastern time, excluding public holidays
• Platform Retainer: four-business-hour response during those hours
• Managed operations: 24/7 emergency on-call for covered systems; for critical outages we aim to investigate, update and attempt resolution within four elapsed hours on a best-effort basis. Resolution within that window is not guaranteed
• Restoration and availability targets, emergency channels and dependency exclusions are contractual under a managed agreement
• The agreement names the covered systems, severity definitions and the engineers on your escalation roster

Security questionnaires, engagement-specific evidence and vulnerability reports go to the security contact published in the security policy and in the security.txt file on this site. Include the affected URL, a description and reproduction steps; do not include subscriber data or credentials.

Security contact and disclosure process

What exists, where it is, and what does not exist yet.

Download the printable security brief (PDF)

Use the architecture review form and select a security, compliance or procurement role, or write to the security contact. A principal engineer replies within one business day with what can be shared and under which terms.