Some things shouldn’t leave the building.
BlakBox is an appliance for answering tenders. It drafts the response from the documents you already keep, and each factual paragraph cites the passages it drew on. Where your documents say nothing, it leaves a marked gap for you to fill.
Get in contact
Want to build it with us?
A fictional defence supplier’s 1,106 documents, split into 4,943 numbered passages, and 15 fictional tenders to answer from them.Open the demonstration
The problem BlakBox solves
Confidential evidence cannot be sent to a cloud service.
The evidence that wins a tender is often the most sensitive material an organisation holds: test results, contracts, certifications and its record of past work. BlakBox runs its models on an appliance on your premises, so none of it is sent to a cloud service.Shown in: Security, where the models runSecurity teams will not approve another connected system.
The box never initiates a connection. It is cabled to one paired computer and answers only the BlakBox app on it.Shown in: Security, network and internetThe evidence is spread across years of files.
BlakBox maps the folders, shares and cloud storage your team already works from into a knowledge graph of your evidence, so there is no content library to build first.Shown in: Product, the ingest stageStatements in a response must be traceable to their source.
Each factual paragraph cites the passages it drew on, and the package includes a citations file that traces each reference to its source document.Shown in: The demonstrationGaps in the evidence surface too late.
Before anything is drafted, BlakBox lists the requirements your files hold no evidence for, while there is still time to close them.Shown in: Product, the gaps stageBid material should not be kept after submission.
A finished tender is passed to your computer once you accept it, and its documents are never stored on the box.Shown in: Security, finished tenders