FORGE is in private beta. This page states the controls that are implemented today — scoped file access, logged downloads, hardened authentication, escrow — and is explicit about the ones that are not yet in place.
You retain full ownership of every design you upload. Operators can only access a file for the specific job they’ve accepted — and they’re bound by terms that prohibit retaining, reusing, or distributing it.
Stored outside the web root on US infrastructure with restricted filesystem permissions, reachable only through the access-checked download endpoint. No CDN, no public bucket. At-rest encryption is on the roadmap.
Operators accept Terms that bar copying, redistributing, or retaining your files beyond what the job requires, and require deletion once the job closes. Per-job NDA attachment is on the roadmap.
Files unlock to the accepting operator only, for the life of the job. Downloads stop once the job is completed or cancelled.
Every download of your file, plus each job state change, is appended to an audit log with the user, timestamp, and IP address.
Your payment sits in escrow until you confirm the parts match spec. No match, no release.
Operators attest U.S.-person status under the Terms and are reviewed by an admin before their account is activated. Repeat QC failures are grounds for removal.
FORGE holds no CMMC certification, no third-party NIST SP 800-171 assessment, no FedRAMP authorization, and no facility clearance. Government work on the platform is limited to unclassified requirements. Below is what is actually implemented, and where the gaps are.
FORGE has not been assessed by a C3PAO and does not hold CMMC certification. The platform is built against 800-171 as a design reference — access control, audit, and identification controls are implemented; media protection and several others are not.
Control gaps are tracked internally by Kapu Solutions Inc. No independent third-party assessment has been performed to date.
Passwords are bcrypt cost-12 with a 14-character minimum. TOTP secrets are sealed with libsodium. All traffic is TLS with HSTS and a restrictive CSP. File contents are not encrypted at rest today.
FORGE never sees, touches, or transmits cardholder data. All payouts and intake handled by Stripe Connect with documented SOC 2.
FORGE’s production track is not yet certified for ITAR, CUI, or classified handling, and the platform enforces no facility-clearance or export-segregation controls. Government jobs are limited to unclassified work.
Compute, storage, and CI all run inside one facility in Honolulu. No third-party SaaS hosts platform data or files. Operators produce and ship from their own shops.
Local accounts with a 14-character password minimum and bcrypt cost-12 hashing, TOTP MFA (required for admins), a 5-attempt / 15-minute lockout, and 30-minute idle plus 8-hour absolute sessions with ID rotation.
Every file access is checked against the job itself — only the buyer or agency that posted it, and the operator who accepted it, and only while that job is open. Every attempt, allowed or denied, is logged.
Every download, job state change, login, and admin action is appended to an audit log with user, timestamp, and IP. Append-only in practice; the log is not cryptographically sealed.
Uploaded files live outside the web root and are only reachable through the download endpoint, which resolves and contains every path before streaming. CSRF tokens on state-changing forms, HSTS, and a restrictive CSP.
Bcrypt cost-12 for passwords. TOTP secrets sealed with libsodium secretbox. TLS in transit. A SHA-256 hash is recorded for every uploaded file and shown on the file list.