CASE STUDY · AUSTELL COWORK · DIGITAL ACCESS

The owner had to be there. Now he doesn't.

Austell Cowork couldn't sell a day pass or onboard a member without someone physically unlocking the door. I built a web-based access control layer — payment, member permissions, expiring digital passes and physical door control in one automated workflow — so the space sells and onboards itself.

My role
Systems Architecture + Full-Stack Build
System
Access automation + API integration
Environment
Real-world physical access
DIGITAL KEEP PASS / LIVE FLOW SYSTEM ONLINE
Austell Cowork
DIGITAL MEMBER ACCESS
Pass valid
API request
DOOR / LOCKED
ready — valid access token detected 200 READY

You could buy in seconds.
You still couldn't get in the door.

Austell Cowork could sell access online, but the final interaction still lived in the physical world. The goal was to remove that disconnect: when someone legitimately has access, the system should know it — and the door should respond.

01 / HANDOFF

Access depended on a physical handoff.

A paid user still needed a separate operational step before they could actually enter the space.

02 / PERMISSION

Access had to be temporary and contextual.

Different products and memberships required different windows of access — not one permanent credential.

03 / HARDWARE

The existing door system had to stay.

The solution needed to extend the physical access stack through software, not force a complete replacement.

No physical handoff.
No wait. No onboarding session.

I treated the door as another endpoint in the business workflow. Payment creates permission, permission creates a time-bound pass, and a validated request triggers the physical action.

SYSTEM TOPOLOGY / DIGITAL KEEP PASS EVENT → PERMISSION → ACTION
01
Checkout
A qualifying product or membership is purchased.
02
Webhook
The backend receives the paid event and checks access rules.
03
Digital Pass
A user-specific access URL is issued with an expiry window.
04
Validation
The backend verifies token, identity and allowed access time.
05
Door API
A validated request calls the access controller and unlocks.
Trigger
Successful paid checkout
Security
Signed / expiring access token
Control
Server-side permission validation
Physical layer
Existing access controller + door

No shared codes. No lockbox.
No one texting a PIN at 7am.

01

Map the access logic

Define exactly which products grant access, how long access lasts, and when the physical location should accept a request.

02

Generate a user-specific pass

Turn a paid event into a digital credential the member can actually use from their phone.

03

Keep control server-side

Never expose door credentials to the browser. The client requests access; the backend decides whether the request is allowed.

04

Bridge software to hardware

Use the access controller's API as the final system action — so a validated digital event becomes a physical unlock.

access-flow.py / simplified
# paid checkout → access credential → physical action

if checkout.status == "paid":
    permission = resolve_access(checkout.product)

    if permission.allowed:
        pass_url = issue_expiring_pass(
            user=checkout.email,
            expires=permission.expires_at
        )

# later, at the door

if validate_pass(token) and within_access_window():
    door_api.unlock(actor=user.email)
    return "access_granted"

The door became part
of the workflow.

Instead of introducing another manual process, the access layer connects the systems Austell already uses to the physical space itself.

01 / AUTOMATED

Digital access issuance

A qualifying purchase can create access without a separate manual handoff.

02 / CONTROLLED

Time-bound permissions

Access can expire based on the business rules attached to the product or membership.

03 / CONNECTED

Physical API action

The web application can securely trigger a real-world door after server-side validation.

04 / COMPATIBLE

Existing access retained

The digital layer extends the current physical system rather than replacing the entire setup.

The shift
One physical door.
Multiple ways in.
One system deciding access.

Architecture through implementation.

Systems Architecture

Design the full path, not just the page.

I mapped the business rules, checkout events, permission model, credential lifecycle, access-time constraints, backend validation, and physical controller integration as one system.

System Design Access Logic API Contracts Security
Full-Stack Build

Ship the layer that connects it all.

I built the web experience and backend integration layer around Stripe events, expiring digital access, user validation and the door control API.

Python / Flask Stripe Webhooks REST APIs

06 — NEXT SYSTEM

Have a physical process
that should be software?

I design the architecture and build the integration layer between business logic, APIs, data and the real-world action.

alex@alexozhyniak.com Book Discovery Call