We Used BioTime, We Suffered, and That's Why We Built Biosensei

Let's be honest: ZKTeco's hardware is excellent. It's robust, durable, and affordable. It's probably the industry standard for a reason. But when it comes time to connect it to software, the story changes dramatically.

For years, we tried working with BioTime and ZKAccess. And while they fulfill their basic function, our experience as developers (and that of our clients) was frustrating. Heavy servers, SQL databases to maintain, complex interfaces, and absolute dependency on being "on-site."

We got tired of fighting against infrastructure. We wanted something that worked like the modern tools we love (like Stripe, Vercel, or Supabase).

So we decided to build it ourselves. That's how Biosensei was born.

1. The Nightmare of Remote Desktop and Local Servers

If you've supported traditional installations, you know this pain by heart:

To fix a simple problem or pull a report, you have to connect via TeamViewer, AnyDesk, or Remote Desktop (RDP) to the client's computer.

• The connection is slow and laggy.
• The client's computer is sometimes turned off.
• The screen resolution breaks.
• It's insecure: Leaving RDP ports open or remote access software running 24/7 is a massive security risk.

With BioTime, you depend on that physical machine (the "server") staying alive. If the hard drive fails, the entire access control operation stops.

With Biosensei, this is over. No servers to maintain. No slow remote desktops. You log into app.biosensei.io from Chrome, Safari, or your mobile, and you have instant total control.

2. Designed by Developers, for Developers 🛠️

What frustrated us most about official solutions was the difficulty integrating them with our own systems (ERPs, custom payroll, gym apps).

In Biosensei, the API isn't an "extra"; it's the core of the product.

While before you had to wrestle with SOAP, intermediate databases, or Windows DLL-based SDKs that don't run on Linux, now you can interact with your hardware through standardized HTTP requests.

Example: Unlock a door via code

Imagine unlocking a door remotely with a simple function, no matter where you are or where the device is:

// This is how easy it is to integrate Biosensei into your App
const unlockDoor = async () => {
  const response = await fetch('https://api.biosensei.io/v1/devices/door/unlock', {
    method: 'POST',
    headers: { 
      'Authorization': `Bearer ${API_KEY}`,
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({ deviceId: 'sn-ZK88291', seconds: 5 })
  });
  
  if (response.ok) console.log("Door unlocked instantly 🚀");
}

3. Fast Connection Without VPNs

With legacy software, connecting a remote branch involved:

• Hiring a Static Public IP (extra monthly cost).
• Configuring a complex VPN between routers.
• Opening ports in the firewall and praying they don't get hacked.

With Biosensei, we changed the game using the ADMS / Push HTTPS protocol:

1. Take the ZKTeco device.
2. Put our URL in the cloud server configuration.
3. Done.

The device makes a secure "handshake" with our cloud and goes online. You can manage a device in Tokyo and another in Mexico City from the same panel, without touching a single router.

4. Frictionless Management

Need to register a new employee? Delete someone who was fired immediately? See who was late?

Everything happens in real-time. Biosensei's interface is designed to be intuitive, fast, and beautiful. Because we believe security software doesn't have to be ugly or hard to use.

Conclusion

We made Biosensei because we wanted to do it right. We wanted the robustness of ZKTeco hardware but with the user experience of a Silicon Valley startup in 2025.

If you're tired of slow remote connections and want to start building real solutions:

Create your free account and connect your first device