Use Case: From 24/7 Access to Smart Time-Based Control

The Challenge

ByteGate was originally designed for Bioflix, a 24/7 unmanned grocery retail chain in Basel. The first four stores—including the Bettingen countryside location—were intended to operate from 6 AM to 11 PM, but access restrictions weren't initially enforced. The straightforward customer base and predictable traffic made strict time controls unnecessary at the start.

Then came the fifth location—and with it, a new requirement.

During the buildout phase of the new Westfeld store, Bioflix faced a practical problem: they needed construction staff and contractors to access the unfinished space, but they couldn't risk registered customers showing up to a store that wasn't ready for business. The location had been announced publicly, and QR codes were already issued to customers in the system.

The question became: Could ByteGate handle selective access control—restricting public entry while allowing staff access during construction, then smoothly transitioning to public operation?

The Solution Development

This wasn't just a feature request—it was an opportunity to make ByteGate more versatile.

We realized that many businesses face similar scenarios:

• Gyms that offer 24/7 access to premium members, but restrict standard members to business hours
• Coworking spaces with different access tiers
• Short-term rentals managing turnover between guests
• Retail stores needing staff-only access outside operating hours

What we needed: A time-based access control system that could:

Recognize different user groups (staff vs. customers)

Apply different rules based on time of day

Handle multiple locations with different schedules

Maintain the fast local processing that made ByteGate reliable

The Technical Evolution

ByteGate's edge computing architecture—where each location processes access decisions locally—meant we needed to rethink how access rules were structured.

Key developments:

• Allowlist/whitelist management: Designating which users have priority access
• Time-restriction logic: Defining and enforcing operating hours per location
• Multi-mode access control: Different rules for different time periods
• Custom messaging: Informing customers when a location is temporarily restricted

The challenge wasn't just adding features—it was ensuring these new capabilities worked seamlessly with ByteGate's existing offline-first architecture. Each controller needed to understand and enforce complex time-based rules even when internet connectivity fluctuated.

The Real-World Implementation

Phase 1 - Controlled Testing (Bettingen Location)

Bioflix and our team decided to test the new time-restriction feature at Bettingen first. While this countryside store had always been intended for 6 AM–11 PM operation, time controls hadn't been strictly necessary given the predictable customer base and simple village setting.

Bettingen became our testing ground. We implemented the 6 AM–11 PM restriction, and the system enforced it successfully—proving that location-specific operating hours were viable within ByteGate's architecture.

Once Bettingen validated the feature, we moved forward with Westfeld deployment.

Phase 2 - The "Staff-Only Access" Challenge (Westfeld Construction)

The Westfeld buildout presented a different challenge: complete public closure while allowing staff access during construction.

We discovered a logic conflict in the existing codebase. The system struggled to interpret a "staff-only" state when the original architecture expected either "open to all" or "closed to all" with specific time windows. The code needed fundamental restructuring to support a third mode: "open, but only to specific users."

The debugging process: We identified that the original 24/7 logic conflicted with the new "whitelist-only" requirement. Resolving this took approximately one week longer than initially planned.

The resolution: After debugging, staff could access the construction site normally as intended. A couple of days later, when Bioflix was ready to open Westfeld to the public, the admin remotely switched the access mode from "staff-only" to "public welcome" through the cloud dashboard.

What this meant technically: This single dashboard action triggered a synchronized update across the entire edge device network integrated with the IoT environment. What happened behind the scenes—how distributed edge devices coordinate access rule changes in real-time while maintaining local autonomy—became a cornerstone feature for managing multiple locations with different access requirements.

We'll explore this IoT synchronization architecture in detail in a future article: "How ByteGate Coordinates Access Rules Across Distributed Edge Devices"

Lessons Learned

Real-world deployment teaches things you can't anticipate in theory.

Communication with urgent client needs:

When a client has an immediate requirement—like Bioflix needing staff access during Westfeld construction—the challenge isn't just technical. It's about understanding what they truly need, estimating what's realistically achievable, and communicating clearly about timing and limitations.

What we learned:

• Listen carefully to the actual use case, not just the feature request. "We need staff access" could mean many different things—understanding the specific scenario prevents building the wrong solution.
• Assess existing system constraints before committing to timelines. A feature that sounds simple might conflict with fundamental architecture decisions.
• Communicate honestly about complexity. When we discovered the logic conflict, we explained the delay and the reason—transparency builds trust more than overpromising and underdelivering.

Technical lesson:

Legacy architecture can become a constraint when requirements evolve. A system designed for one primary use case (flexible public access) may need significant rework to support opposite scenarios (selective access). This is normal in software development—the key is recognizing these conflicts early and adjusting timelines accordingly.

Current Capabilities

Today, ByteGate supports:

✓ Location-specific operating hours with automatic enforcement

✓ User tier management (staff, premium members, standard members, temporary guests)

✓ Allowlist/blocklist control for security and special access

✓ Time-limited access codes for contractors, deliveries, or trials

✓ Custom door messages based on time and user status

✓ Multi-location management with independent schedules

✓ Remote access mode switching - change access rules across all locations from the dashboard

✓ "Staff-only" mode for construction, maintenance, or special events

Who Benefits

This evolution makes ByteGate valuable for:

• Unmanned retail - Staff access for restocking outside customer hours, or during store setup
• Fitness facilities - Tiered membership with different access windows
• Coworking spaces - Premium vs. standard member access levels
• Short-term rentals - Automated guest turnover with cleaning crew access
• Event spaces - Setup/teardown access separate from event access
• Construction/renovation - Staff-only access during buildout phases

Looking Forward

ByteGate continues to evolve based on real-world use cases. We're currently refining:

• Enhanced integration with existing CRM systems
• More granular access scheduling options
• Expanded analytics for traffic pattern analysis
• Additional hardware compatibility for diverse installation environments

Our approach is practical: solve real problems for real clients, then make those solutions available to others facing similar challenges. We prioritize honest communication and realistic timelines over overpromising features we can't deliver reliably.

Want to understand how ByteGate's edge-cloud architecture works?

We're preparing a technical deep-dive on how distributed edge devices synchronize access rules while maintaining local processing autonomy.

Subscribe to our updates to be notified when it's published.

Interested in ByteGate for your business?

We work closely with clients to understand your specific access control needs and develop solutions that actually work for your operations. Contact us to discuss how ByteGate can adapt to your requirements.

Schedule Consultation