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
Step 1: Confirm release availability
Full public stable release is the destination, but it and public AWS Marketplace access are not yet available. Request the buyer/procurement pack to confirm the current release and delivery posture.
Step 2: Prepare your environment
We will confirm the approved deployment path for your environment. Select instance type, region, VPC, and subnet per your change controls.
Step 3: Boot the appliance
Boot runs docker-compose via systemd. The appliance listens on port 8080 (configurable), with optional Prometheus on 9090.
Step 4: Run a test
Upload sample data or a sandbox dataset. Produce the PDF report, evidence manifest (SHA-256), and checksum log.
Step 5: Confirm delivery terms
Confirm the available version, delivery path, licensing, and support terms. Any pre-release evaluation or private handoff is separately approved; it is not the product destination.
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 demo release: v5.0.0-rc9-public-fix-2724455 (non-commercial prerelease). Public demo materials are selected synthetic/demo assets from that public release, including the demo report; supporting run packs and intake diagnostics are linked from FL-BSA documentation. They are not customer output, legal advice, or proof of a public Marketplace launch.
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.