Attila Tokolics / Solo developer

One engineer.
The whole system.

I design the database, build the app and run the servers. My software tracks work on factory floors, in warehouses and on jobsites, and it powers Eventonite, the ticketing product I run myself.

Now running
Background
Manufacturing engineer
Taking on
One or two clients at a time
Built with
React, Node.js, PostgreSQL, AWS
My own product / Live

Eventonite

Tickets for club nights and festivals. One flat monthly fee, zero cut of your sales.

Eventonite is my own product, designed, built and run by me. Ticket money lands in the organizer's own Stripe account, and the door scanner keeps working when the signal drops.

$29flat monthly fee to start
$0added to the ticket price
23languages for tickets and emails
eventonite / check-in.tsExcerpt
// A partial unique index allows one live "ok" per ticket:
// two doors at once, one gets in. Retries write nothing.
export const checkInTicket = async (input: CheckInInput) => {
  const ticket = await findTicket(input);
  const ticketId = ticket?.id ?? null;
  const resultKey = getResultKey(ticket, input.eventId);

  let checkIn =
    resultKey === "ok" && ticket
      ? await insertLiveCheckIn(input, ticket.id, …)
      : await insertCheckIn(input, resultKey, ticketId);

  if (!checkIn) {
    const replay = await db.query.checkIn.findFirst({
      where: { idempotencyKey: input.idempotencyKey },
    });

    // Not a retry: another door was faster
    checkIn =
      replay ??
      (await insertCheckIn(input, "alreadyCheckedIn", ticketId));
  }
Two doors scan the same ticket at the same moment. Exactly one gets in.
01

Set up

Create the event and its ticket types, each with its own price, quantity and sales window.

02

Sell

Your branded ticket site handles mobile checkout and sends QR PDF tickets in 23 languages.

03

Get paid

Ticket money goes straight to your own Stripe account. Eventonite bills a flat monthly plan.

04

Run the door

Staff open the scanner with no app store and no account. It works offline after one sync.

What changed after the software shipped.

SystemBeforeAfter
CL Logistics Manager

Bulk imports, labels and reports took hours of spreadsheet work.

They run as background jobs in minutes and email the team when done.

GzoneAI

An hour of manual data entry to turn a project description into parts.

A background job finishes it in seconds.

CL Factory Manager

FTP import failures went unnoticed for hours.

An email alert goes out as soon as the sync goes stale.

CL Factory Manager

Truck loading had no enforced sign-off.

The driver scans, the manager approves. Unsigned shipments are gone.

M-Pakk Manager

Invoices were typed in by hand.

They generate through the API when an order completes.

CL Jobsite Installer

Project managers phoned the site for status updates.

They check live status and photo galleries from a laptop.

What I can build for you.

ERP and order management

Orders, purchasing, inventory, invoicing and role-based dashboards in one system.

M-Pakk Manager →

Factory-floor tools

Station screens, barcode scanning, Zebra label printing and live job tracking.

CL Factory Manager →

Warehouse and logistics

Multi-warehouse stock, pick lists, transfers and approval workflows with a full audit trail.

CL Logistics Manager →

Offline field apps

Installable web apps that save on the device first and sync when the connection returns.

CL Jobsite Installer →

AI data extraction

Turn unstructured text into structured records, with an alert when a job finishes or fails.

GzoneAI →

SaaS products

Paid products with checkout, team roles, multiple workspaces and translated customer emails.

Eventonite →

You work with the person who writes the code.

I know the factory floor

I was a furniture manufacturing engineer before I wrote software. You won't spend the first month explaining what a work order is.

Nothing gets lost between teams

Database, frontend, infrastructure and deployment sit with one person. No handoffs, no account managers, no agency markup.

You talk to me

I take on one or two clients at a time, so when something breaks you reach the person who can fix it.

Monthly retainer

I stay on as your technical partner. New features, maintenance and fixes from someone who already knows your system.

Fixed project

One system or module, with an agreed timeline and clear deliverables. Right for a new build or a major feature.

How a project runs.

1

Learn the operation

I start with how the work really moves through your business, before any code.

2

Agree the scope

We pin down one system or module, a timeline and clear deliverables.

3

Build and deploy

Database, app, infrastructure and CI/CD, all from the same person.

4

Keep it running

A monthly retainer covers maintenance, fixes and new features once it's live.

The tools I ship with.

Frontend

React, Next.js, Vite, Ant Design, React Query, Redux

Backend

Node.js, REST APIs, BullMQ + Redis, CASL

Data

PostgreSQL, MySQL, MongoDB, IndexedDB, Sequelize

Cloud

AWS S3, SES, Secrets Manager, Parameter Store, PM2, CI/CD

Integrations

Stripe, Monday.com, Shoprenter, Billingo, OpenAI, Zebra printers

Portrait of Attila Tokolics
About

From the factory floor to production code.

I'm Attila. I started as a process engineer in furniture manufacturing and taught myself to code to fix problems I saw firsthand on the floor.

That background shapes everything I build. Production flow, subcontractors and jobsite coordination are things I've lived with for years, so the data model follows how your business really runs.

Alongside client work I build and run my own product, Eventonite. Same approach: one person, the whole system.