Blazelock Beta Is Now Available

Today we are opening beta access to Blazelock. Our malware scanning API for applications, file uploads, and secure product workflows.

Blazelock is built for teams that need to accept files without turning malware scanning into another infrastructure project. Instead of running and maintaining your own scanning layer, you send files to the Blazelock API, receive structured scan results, and keep your upload flow moving with clear security signals.

The beta is free until our public release, currently planned for Q4 2026. It is also the best time to try Blazelock early and help shape what we build next.

What Blazelock Does

Modern products accept files everywhere: onboarding forms, support portals, document workflows, internal tools, customer uploads, and automated background jobs. Every one of those entry points can become a security risk if files are stored, processed, or shared before they are checked.

Blazelock adds malware scanning to those workflows through a simple REST API. You can submit files, retrieve scan results, connect webhooks, and build malware detection into your own systems without operating scan engines yourself.

Blazelock is designed around a few practical principles:

• Fast integration through a clear API.
• Flexible scan modes for both background workflows and request-response flows.
• European infrastructure with servers located in Germany.
• Scan engines from market-leading providers that we continuously evaluate for detection quality, false-positive behavior, and performance.

You can explore the API, endpoint reference, authentication model, and integration guides in the Blazelock documentation.

Join the Blazelock Beta

Registration is currently limited to approved beta users. Join the waitlist on blazelock.com, and we will send your personal invite shortly so you can start using Blazelock and share feedback early.

During the beta, Blazelock is free to use. You can create your account, generate API keys, and start testing real file scan workflows.

Beta access means:

• You can use Blazelock without paying during the beta period.
• Your feedback directly influences the product, documentation, and pricing model.
• You get early access to new dashboard and API improvements as they become available.

A First Look at the Dashboard

The Blazelock Dashboard is the control center for your account. It helps you manage integrations, configure API keys, review scan activity, and keep your setup understandable as your product grows.

Using the API

Blazelock supports two scan modes. In most production integrations, asynchronous scans are the better default because your application can continue working while the scan runs. For flows that need an immediate result inside the same request-response cycle, synchronous scans are available too.

Both JavaScript examples use an API key created in the Blazelock Dashboard. Keep API keys server-side and send them as bearer tokens.

Asynchronous Scan Example

Use the asynchronous endpoint when your application can track the result later through webhooks or status polling.

import { readFile } from 'node:fs/promises'

// Build the multipart upload payload.
const form = new FormData()
const attributes = { file_name: 'invoice.pdf' }
form.append('attributes', new Blob([JSON.stringify(attributes)], { type: 'application/json' }))
form.append('file', new Blob([await readFile('./invoice.pdf')]))

// Submit the file for asynchronous scanning.
const submitResponse = await fetch('https://api.blazelock.com/v1/file-scans', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.BLAZELOCK_API_KEY}`,
  },
  body: form,
})

let scan = await submitResponse.json()

// Poll until Blazelock returns a terminal status.
while (scan.status === 'processing') {
  await new Promise(resolve => setTimeout(resolve, 2000))

  const statusResponse = await fetch(`https://api.blazelock.com/v1/file-scans/${scan.id}`, {
    headers: {
      Authorization: `Bearer ${process.env.BLAZELOCK_API_KEY}`,
    },
  })

  scan = await statusResponse.json()
}

console.log(scan.id, scan.status)

The response returns the created scan in processing state together with its scan ID. Your application can continue immediately and react when Blazelock sends a webhook event or when your backend checks the scan status.

Synchronous Scan Example

Use the synchronous endpoint when the caller needs a terminal result during the same request.

import { readFile } from 'node:fs/promises'

// Build the multipart upload payload.
const form = new FormData()
const attributes = { file_name: 'invoice.pdf' }
form.append('attributes', new Blob([JSON.stringify(attributes)], { type: 'application/json' }))
form.append('file', new Blob([await readFile('./invoice.pdf')]))

// Submit the file and wait for a terminal scan result.
const response = await fetch('https://api.blazelock.com/v1/file-scans/sync', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.BLAZELOCK_API_KEY}`,
  },
  body: form,
})

const scan = await response.json()

console.log(scan.id, scan.status)

Synchronous scans are useful when the user experience depends on an immediate answer. The endpoint waits for the scan result and returns it in the same request when available.

What Comes Next

The beta is where we validate Blazelock with real teams and real workflows. Over the coming months, we will keep improving the dashboard, expanding integration guidance, and tuning the product around practical developer feedback.

Our public release is currently scheduled for Q4 2026. Beta users will receive a special discount at public release as a thank-you for their early trust and feedback.

If malware scanning is part of your upload flow, product security roadmap, or internal operations work, now is the right time to try Blazelock. Join the beta, connect your first integration, and help us build a faster, cleaner way to keep harmful files out of applications.