Federal Executive Summary
Technology, systems development, research, engineering, operational execution.
SSDF INC. is the parent and holding company — a Florida C-Corporation organized to develop, operate, and contract technology, research, engineering, and operational capabilities across multiple federal procurement markets. AMAIMA INC. is its wholly owned operating subsidiary and technical flagship. It operates as a developer and prime-contractor organization rather than a single-product software company.
Discover→ Qualify→ Price→ Resource→ Contract→ Execute→ Verify→ Deliver→ Invoice→ Repeat
The sequence is the operating model. It is not a claim that SSDF already holds every person, license, certification, or piece of equipment a solicitation may require.
01 — Identity
Federal identity
- UEI
- WBXSLSMUYE29
- CAGE
- 25J93
- SAM.gov
- ACTIVE
- SAM renewal
- September 18, 2027
- Legal entity
- SSDF INC. — Florida For-Profit C-Corporation
- Role
- Parent / Holding Company
- Operating company
- AMAIMA INC. — wholly owned Florida C-Corporation
- DUNS
- 14-790-8413
- Disaster registry
- Yes — all of the United States
02 — Structure
Parent, operating company, portfolio
SSDF INC. is the parent and holding company. AMAIMA INC. is its wholly owned operating subsidiary and technical flagship. Both are separately incorporated Florida C-Corporations. Ownership is the hierarchy.
- Parent / Holding
- SSDF INC. — Florida C-Corporation. Corporate, IP, systems-development, contracting, and orchestration. The federal prime sits here.
- Operating company
- AMAIMA INC. — Florida C-Corporation, wholly owned. Technical flagship: cryptographic AI, systems engineering, research, and operational technology. A corporation, not a product line.
- Portfolio
- BasisGuard, MNEMOS, SSDF Transportation (ssdftransport.site — dispatchers, carriers, brokers, and truckers), Digital Commerce, StackDesk, Genesis Engine. Business lines, platforms, and systems of SSDF INC. Not separate corporations. Transportation is not a motor-carrier claim.
- Internal
- SSDF AB — discovery infrastructure. SSDF O2O — internal opportunity-to-obligation system at ssdfo2o.site. Neither is a separate corporation or a public product.
03 — Lanes
Eight federal capability lanes
Families, not a dump of every code. The taxonomy lives on the codes page.
A — Digital Technology
Software publishing, custom programming, systems design, infrastructure, SaaS.
B — Cybersecurity, Network & Telecom
Cryptographic infrastructure, verification, sovereign deployment, satellite trust. DG11 is a technical capability, not a carrier claim.
C — Scientific & Technical R&D
Applied research and experimental development in cryptography, AI, quantum-classical systems, and verification.
D — Professional, Program & Business Support
Program management, engineering support, data collection, accounting, auditing, acquisition support where actually offered.
E — Logistics & Transportation
Transportation-dispatch and operational control. SSDF does not automatically represent itself as the carrier.
F — Facilities & Physical Services
Potential operating lanes fulfilled through qualified resources. A code is not a payroll claim.
G — Workforce
Capability-building lanes for placement and temporary help — not a conventional staffing agency claim.
H — Digital & Physical Commerce
Digital products, licensing, credentials, research, and physical-product fulfillment evaluated per solicitation.
04 — Engagement
Structured to the requirement
Time & Materials
Architecture, engineering, research, consulting, program support.
Fixed-price deliverables
Defined software, infrastructure, verification, or operational output.
Software licensing
SSDF / AMAIMA components, including FHE, attestation, and verification.
SaaS / usage
Platform and TaaS services on recurring or usage structures.
Sovereign deployment
Domestic or controlled deployment of cryptographic and AI infrastructure.
Operations / fulfillment
SSDF-managed execution using permitted internal and partner resources.
05 — Decision rule
Four questions before a bid.
- 01Can SSDF legitimately contract to deliver the requirement?
- 02Can SSDF obtain the required people, equipment, facilities, licenses, certifications, and other resources?
- 03Can SSDF perform directly or through employees, independent contractors, qualified subcontractors, vendors, or teaming partners where permitted?
- 04What solicitation-specific limitations prevent or condition that structure?
Only then: price, contract, execute. Capability is not authorization. Contract-specific rules control.
06 — Disaster response
Registry: yes. Geography: all United States.
The Disaster Response Registry is an additional federal distribution channel — not a claim that SSDF maintains every emergency-response resource in every location. The operating model is the same: requirement → scope → qualification → build/buy/partner → labor and equipment → SSDF control layer → execution → evidence → delivery → invoice.