IMPLANTOS/THE JOURNEY

AN ONGOING EXPERIMENT BY CLAYTON SZAKACS

EST. 2026

A small connection.
A bigger possibility.

What happens when technology becomes personal?
This is my journey from curiosity to a connection
I’ll eventually carry in my own hand.

↓
PRE-INSTALL / HARDWARE IN HANDUpdated September 30, 2026 · Professional installation next

01 / THE REASON

A little science fiction.
A real starting point.

Games like Cyberpunk made me curious about a world where technology becomes part of us. Purchasing a Dangerous Things NExT v2 was my small step from imagining that future to exploring what I could actually build.

I’m Clayton, a marketing student learning through a project that feels personal. I want to understand the technology, make the experience my own, and document the decisions along the way.

Clayton Szakacs
Clayton SzakacsCuriosity → experimentation → experience

02 / FIELD NOTES

An idea becomes something real.

LATEST FIRST

The hardware is here. The next chapter is physical.

Purchased. Delivered. Preparing for installation.

My Dangerous Things NExT v2 package has arrived. I have the sterile implant/injector package, a Proxmark3 Easy, a KBR1 HF/NFC reader, T5577 and NTAG216 test cards, and repeater stickers in hand. The project has moved from waiting for a package to preparing for professional installation. The implant is not installed yet.

The first destination is already decided: https://tap.clayszak.com. After installation, and when ready for use, I plan to write that URL to the NFC side and test the experience with compatible phones. The site can keep evolving behind the same address.

I own clayszak.com through Cloudflare. Tap is the public landing page; Journey is the independent story and portfolio site. The landing page has been refined around the clean layout I preferred, with the newer, longer profile and ImplantOS animation treatment. It works on normal networks and cellular, while PCC Wi-Fi blocks the custom-domain sites—a reminder that the network is part of the visitor experience, too.

Beyond the first phone tap, I want to build PC workflows with the KBR1, room and smart-home automations using Raspberry Pi or ESP32 readers with Home Assistant, and authorized RFID/NFC experiments with the Proxmark3. Those are planned builds, not working implant features yet.

WHY THIS MATTERS

For me, the biohacking is the starting point. The case study is what I build around it: a memorable introduction, a useful digital experience, and real experiments that connect marketing with technology. I want to document what people understand, where they hesitate, and whether the interaction is worth repeating.

Three choices. One clear introduction.

01 CONNECT. 02 SOCIAL. 03 IMPLANT.

The landing page at tap.clayszak.com now gives each visitor a choice. CONNECT is for saving my details or reaching me. SOCIAL is for exploring my public and professional presence. IMPLANT explains the technology behind the idea.

Separating those intentions removes the competition between a contact card and social links. Each page has one job, more breathing room, and a small BACK link to the hub.

The original 2.6-second sliced-text intro stays on the landing page. Black and charcoal, white and gray, strong spacing, restrained border changes, moving arrows, and an understated glass/reflection effect give the tap experience its edge. The direction is minimal and personal, without gamer or cyberpunk styling. Reduced-motion preferences are respected.

THE DESIGN DECISION

A quick introduction should let people choose their next action. The deeper project story stays here on Journey.

A contact card worth keeping.

A digital business card with a practical next step.

The premium card has its own home at /contact, pairing my portrait with a subtle reflective surface and a prominent ADD TO CONTACTS action.

Clayton Szakacs · Marketing
clay@clayszak.com
678-673-0786
tap.clayszak.com

The save action downloads a photo-enabled vCard containing my contact details. The visitor’s device handles the final confirmation to add it to their address book. Email and phone links are also available directly.

The separate /social page keeps just two destinations: Instagram @clayszak and Clayton Szakacs on LinkedIn.

My domain becomes personal infrastructure.

One identity across the web and email.

I own clayszak.com and use Cloudflare to manage its DNS. The domain gives the project a stable identity: tap.clayszak.com for the NFC/personal identity hub, and journey.clayszak.com for this project journal.

Cloudflare Email Routing forwards mail addressed to clay@clayszak.com into Gmail. Receiving mail is working. I chose to keep Gmail as my destination inbox so the public address can change without changing where I manage messages.

Sending as the custom-domain address is a separate future capability; incoming forwarding alone does not provide outgoing mail. The domain, website, and email are connected parts of the identity, with different responsibilities.

One project. Two destinations.

The tap should be simple. The story deserves room.

The first website tried to introduce the project and tell the whole story in one place. As the identity experience took shape, those became two different needs.

Now the direction is clear: tap.clayszak.com is the quick introduction. journey.clayszak.com is where I document the build, what I learn, and what comes next.

THE DESIGN DECISION

Give someone arriving from a tap a clear next step. Give someone who’s curious a deeper story.

From a demo to my identity.

The landing page became something that actually feels like me.

The initial V1 paired my photo and name with two focused modes: Identity and Implant. Identity opens my Instagram and LinkedIn. Implant explains the hardware in a concise, approachable way.

The design is black-on-black, with a brief sliced-text introduction. It’s been published, and the editable files are saved in the ImplantOS repository. The photo, links, and content can evolve as the project does.

Open the tap experience ↗

The first working version.

Before testing the hardware, I needed somewhere for the connection to lead.

With AI coding assistance, I built the first mobile-first website: a browser demo, an explanation of the idea, and my first journal entry. That initial implementation was merged into the GitHub repository.

It made the idea tangible. I could open a real page in a normal browser, think about what a visitor would understand, and start refining the experience before an actual NFC tap.

Learning how the code works—and making changes myself—is part of this project, too.

Before the first tap.

It started with a fascination for body tech—and the chance to build something of my own.

I purchased the NExT v2 and started exploring what I could do with it. The idea of carrying a connection to something I built in my own hand was what drew me in.

“I want to understand what I can build with this technology—and learn by making it my own.”

At the start of this journal, I was waiting for the implant and exploring installation arrangements. No physical NFC tests had happened yet. The first step was the web experience.

I’m documenting this for anyone curious about the project, and as a record of how I approach an idea: the decisions, experiments, setbacks, and results as they happen.

03 / CURRENT ARCHITECTURE

One domain. Focused destinations.

AS OF SEP 30, 2026

clayszak.com is my domain, owned through Cloudflare. Cloudflare DNS connects each web hostname to its hosted site. Tap and Journey are separate sites; the pages inside Tap share one hostname.

A subdomain is the part before clayszak.com, such as tap or journey. A route is the path after that hostname, such as /contact. Adding a route to the existing tap site needs no new DNS record. A new subdomain needs its own hosting and DNS connection.

THE CONNECTION

Planned NFC tap → compatible phone opens tap.clayszak.com → visitor chooses CONNECT, SOCIAL, or IMPLANT.

Email follows a separate path: clay@clayszak.com → Cloudflare Email Routing → Gmail.

04 / PROGRESS & POSSIBILITIES

Hardware in hand.
Installation ahead.

In hand / live

  • NExT v2 purchased and delivered, with the sterile implant/injector package.
  • Proxmark3 Easy, KBR1 HF/NFC reader, T5577 and NTAG216 test cards, and repeater stickers in hand.
  • Owned clayszak.com domain and Cloudflare DNS setup.
  • Tap hub with /contact, /social, and /implant routes.
  • Photo-enabled vCard, contact links, Instagram, and LinkedIn.
  • Clean landing layout refined with the newer profile and ImplantOS animation treatment.
  • Journey as a separate project journal.
  • clay@clayszak.com receiving mail through Cloudflare into Gmail.

Planned / under consideration

  • Professional installation, then writing https://tap.clayszak.com to the NFC side and testing with compatible phones.
  • KBR1-triggered PC workflows for work, gaming, and focus.
  • Room and smart-home automation with Raspberry Pi/ESP32 readers and Home Assistant.
  • Authorized RFID/NFC experiments with the Proxmark3 and test cards.
  • Outgoing custom-domain email while keeping Gmail as the destination inbox.
  • Resume, work, and reel routes to expand the portfolio.
  • Dynamic NFC destinations: change what a stable URL opens without rewriting the chip.
  • Analytics to learn which pages help visitors; visits alone would not prove an NFC scan.
  • QR codes pointing to a stable URL, plus custom short links.
  • Private pages with access controls and API endpoints for future integrations.

Current stage: pre-install. The implant is not installed, and implant URL writing, phone testing, and automation builds are still ahead. Tap is live on normal networks and cellular; PCC Wi-Fi blocks the custom-domain sites.

05 / PORTFOLIO CONTEXT

Making an idea
useful to someone else.

ImplantOS connects my interest in technology and biohacking with marketing: how people first encounter an identity, what they need to understand, and how easily they can take the next step.

The project demonstrates information architecture, personal branding, domain and email setup, responsive design, and iteration with AI coding assistance. The useful evidence is the working experience and the decisions behind it. Visitor feedback and measured outcomes come next.

06 / WHAT COMES NEXT

The first real tap
is still ahead.

The web experience is live and the hardware is here.
Now I’m preparing to connect the two.

  1. 01

    Professional installation.

    Arrange professional installation of the NExT v2. This is the next milestone; installation has not happened yet.

  2. 02

    Write the URL. Test the tap.

    After installation, when ready for use, write https://tap.clayszak.com to the NFC side. Test compatible phones, contact saving, and the experience across networks, then document actual results.

  3. 03

    Build useful automations.

    Start with KBR1 PC workflows, then explore Raspberry Pi/ESP32 and Home Assistant room automations. Use the Proxmark3 for authorized experiments and turn the results, limitations, and visitor feedback into portfolio evidence.

THE IDEA, SIMPLY

A link is the beginning.

The planned NFC interaction shares a web address. The phone opens the website, where the experience lives and can keep changing. Opening the page today works in a normal browser; it doesn’t mean a physical scan has happened.