Getting Started
Procurement & Deployment
FL-BSA is being prepared for a full public stable release. Until it is published, request the buyer/procurement pack to confirm current availability. The intended AWS deployment is AMI-first, with supported container/VM paths agreed separately.
Deployment steps
Confirm release availability
Full public stable release is the destination, but it and public AWS Marketplace access are not yet available. Request the buyer pack to confirm the current release and delivery posture.
Agree terms and delivery approval
Confirm the available version, delivery path, licensing and support terms. Any pre-release evaluation or private handoff is separately approved.
Prepare your environment
Confirm the approved deployment path, instance type, region and network boundaries under your change controls.
Install the agreed artifact
Follow the runbook for the approved version and delivery path. The current container service listens on port 8080 (configurable), with optional Prometheus metrics on 9090.
Run the agreed test
Use the approved synthetic or sandbox inputs. Produce the report, evidence manifest and checksum log, then review the result against the agreed acceptance criteria.
Procurement package
Evidence bundle
- Evidence manifest: JSON manifest and PDF report with embedded hashes.
- Infrastructure: BOM and network diagram (request access).
- Control mapping: FCA, EU AI Act, and ECOA checkpoints.
Commercials
- Commercial terms: Finalized during qualification; annual, multi-year, and Marketplace structures are post-qualification options where supported by the release path.
- Optional evaluations: Separately scoped before release with an agreed duration and success criteria.
- Private Offer support: Custom terms or multi-entity rollouts where supported by the release and procurement path.
Public sample report: corrected, report-only bounded synthetic/demo prerelease v5.0.8-report-fix-20260929. The linked demo report is not customer output, legal advice, or proof of a public Marketplace launch. The full technical whitepaper and verification companion in FL-BSA documentation use the separate public technical-characterization prerelease v5.0.8-technical-whitepaper-20260930; their disposition remains characterization_only.
Deployment options
AWS AMI-first
Intended AWS deployment path. Before public release, any AMI evaluation or private handoff requires separate approval. The single-tenant image provides deterministic boot, reporting services, and integration with customer IAM.
Container / VM deployment
Available for private, controlled, or non-AWS deployments where agreed. Docker Compose stack (API, worker, Redis) using the selected CPU-based v5 runtime. GPU acceleration is not part of the selected native runtime.
Plan ingress/egress rules, IAM roles, and subnet sizing with your network team. We provide implementation runbooks on request.
Need a walkthrough?
Procurement reviews commonly cover control objectives, evidence bundling, and internal audit mapping. We provide templated questionnaire responses and written walkthroughs.