Skip to content

Winglark

Independent event technology startup

Events have many moving parts. Winglark brings them together.

Winglark is an event operations platform for invitations, guest management, RSVPs, communications, access and on-site operations — designed for individuals, teams, companies and agencies.

Contact WinglarkRequest Early AccessExplore the platform
On the left, the separate tools an event is usually run with. On the right, the one line of work Winglark keeps them in: invite, reply, communicate, admit, report.
Started
2026
Stage
Early Access
Product
Event operations software
Operating from
Türkiye
European company structure
Planned in Estonia
Contact
info@winglark.com

Our company

An early company with a serious product.

  • Early company.
  • Serious product.
  • Real infrastructure.
  • A long-term direction.

Winglark began with a simple observation: running an event still takes too many disconnected tools, spreadsheets, messages and manual handoffs. The guest list lives in one file, the invitations in another tool, the replies in an inbox and the door list on paper.

Winglark is an independent event technology company, started in 2026, that brings those pieces into one operating layer. The guest an organiser adds is the same record that receives the invitation, holds the reply, is admitted at the door and appears in the report afterwards.

The product runs today on real production infrastructure and is in Early Access: organisations are admitted on request while the platform grows with them. Winglark operates from Türkiye, and its European company structure is planned in Estonia.

One guest record, from the first invitation to the last guest through the door.

Why Winglark exists

Event operations are still split across tools that do not talk to each other.

Most events are run across a handful of tools, each holding part of the truth. Somebody copies between them by hand, and the copy is where things go wrong.

  • Spreadsheets
  • Disconnected email tools
  • Messaging apps
  • Separate RSVP forms
  • Manual guest lists
  • Stand-alone check-in apps

Winglark replaces the copying, not the people.

Our aim is not another planning app. It is the operations infrastructure underneath an event: the list, the messages, the replies, the door and the record of what happened — kept in one place, under one set of permissions.

So that the people running an event can do it with more control, more clarity and fewer surprises on the day.

What we build

One product, organised around the life of an event.

Winglark is made of modules that share one guest record. They are grouped here by the job they do for an organiser, not by the order in which they were built.

  1. Plan and organise

    The structure an event sits on: who the organisation is, who may do what, and what to do next.

    • Event & Guest

      Events with a date, a venue and a capacity, and the guest list that belongs to each one.

    • CompanyHub

      The organisation’s profile, brand and team roles — and, for agencies, a separate space for every client.

    • Compass

      Next steps chosen for the person and their role, marked done only when the work really exists.

  2. Invite and communicate

    Getting the right invitation to the right person, and knowing that it arrived.

    • TemplateForge

      Invitation design that holds together across email clients, with the organisation’s brand applied.

    • AI Studio

      Drafts invitation copy and imagery from the event’s details, for the organiser to edit and approve.

    • MailFlow

      Sending from verified senders only, with delivery, bounces and opt-outs recorded for every guest.

    • InvitePulse

      When the list changes, works out who needs an invitation and who already has one.

    • ConnectFlow

      Channel permissions kept per person. Email is the channel in use; SMS, WhatsApp and RCS are configured and not sending yet.

  3. Manage guests

    A list that can be trusted before anyone is invited, and kept accurate as replies arrive.

    • ListGuard

      Reads an imported list and reports duplicates, broken addresses and blocked contacts before anything is saved.

    • Event & Guest

      Replies, plus-ones and answers kept on the same guest record the door will check.

  4. Operate the door

    The part of an event that happens in real time — often with a weak connection and a queue.

    • GatePass

      QR check-in for every entrance, door staff who see only the door screen, and entry that keeps working offline.

  5. Monetise events

    For events where some guests pay to attend.

    • TicketFlowactivated with our team

      Ticket types and paid entry on the same guest record, activated together with our team rather than by self-service.

  6. Understand and grow

    Staying in touch with people over time, with every opt-out respected.

    • ReachLabnot switched on yet

      Segments built from guest data, and campaigns prepared and previewed with opt-outs applied to every recipient.

  7. Platform

    What every other module stands on.

    • LedgerCore

      Plans, allowances and usage: what each workspace includes and how much of it has been used.

    • LocaleCore

      Five languages across the product, the invitations and every guest’s own pages.

Where a module is not switched on for everyone, it says so beside its name. Nothing on this page is described as available before it is.

Built for different events

From a birthday to a conference, the same operating layer.

Every kind of event asks different questions of its guests and of its door. Winglark has a page for each of the twenty-five event types it supports, describing what that event needs.

Explore event types

Who it is for

Built for the people who actually run the event.

Winglark is designed for five kinds of organiser, each with a different reason to want one dependable list.

  1. Individual organisers

    A wedding, a birthday, a private dinner: one person, one guest list, and invitations as considered as the occasion.

  2. Small businesses

    A launch or an opening run by a small team, without stitching a form, a mail tool and a spreadsheet together.

  3. Companies

    Corporate events under the company’s own name, with roles for the team and a clear report for whoever asks afterwards.

  4. Agencies

    Several clients’ events in one workspace, with each client’s data kept apart on the server.

  5. Venues and event teams

    Recurring events, several entrances and door staff who need a fast screen rather than a back office.

Product stage

Early Access

Winglark is currently in Early Access. Organisations are admitted on request, so that every new workspace is set up with care while the product keeps growing.

Request Early Access

Plans, and what each one includes, are published. See pricing

  • Core production infrastructure is live

    The application, the database, email delivery and sign-in run in production at winglark.com.

  • Real event workflows are operational

    Events, guest lists, invitations, replies and QR check-in are used for real events today.

  • The platform keeps expanding

    New capabilities are released progressively, shaped by real operational use and ongoing product development.

The team behind Winglark

A small, independent team.

Winglark is being built by a small independent team working across product, design, engineering and event operations.

Our size keeps us close to the product. It lets us make deliberate decisions, hear directly from the people who use Winglark, and build without layers of process that would not help anyone run a better event.

How we build

The principles we hold ourselves to.

These are working rules rather than slogans. Each one changes how a feature is designed, tested or released.

  1. Security before convenience

    When a shortcut would weaken a boundary between organisations, the boundary wins.

  2. Real behaviour before marketing claims

    This website describes what the product does today. What is not switched on is labelled that way.

  3. Human review in important decisions

    Product, security and production changes are reviewed by people before they ship.

  4. Privacy-conscious development

    We collect what an event needs, and measurement on our own website waits for a visitor’s consent.

  5. Progressive release

    Capabilities are switched on step by step, once they work, not all at once.

  6. Safe production changes

    Database changes are additive and tested first, and production data is never used for testing.

  7. International from the start

    Five languages are part of the architecture, not a translation added at the end.

  8. Accessible experiences

    Keyboard access, readable contrast and reduced motion are part of what “done” means.

  9. Responsible use of AI

    AI assists the people who use Winglark and the people who build it. It does not decide for them.

Responsible AI

AI is a tool inside the product, not the product itself.

AI Studio works inside TemplateForge, where invitations are designed. It helps with a first draft; the organiser decides what is used.

  • Developing an invitation concept
  • Generating imagery for an invitation
  • Preparing invitation copy, in five languages
  • Moving faster through creative work

Dates, times and venues always come from the event record, and nothing generated is used until the organiser has edited and approved it. Human creativity and judgement stay in charge.

AI Studio’s text and images are generated by OpenAI models. Guest data is not sent to them.

AI-assisted development

Building with modern AI tools.

Claude and Claude Code are part of Winglark’s development workflow across engineering, product research, documentation, testing and quality assurance.

Important product, security and production decisions remain subject to human review.

Technology and infrastructure

Built on modern, established infrastructure.

Winglark runs on established providers, each chosen for one job. This is what we use each of them for — nothing more is implied.

Vercel
Hosts and delivers the application; its functions run in the EU (Frankfurt).
Neon · PostgreSQL
Managed PostgreSQL for the production database, hosted in the EU.
Prisma
The data layer between the application and PostgreSQL, with additive, reviewed schema changes.
Resend
Sends invitations and system email, and receives mail sent to Winglark’s own address.
Google OAuth
Sign-in with Google, using OAuth 2.0.
PostHog
Analytics on this website, only for visitors who consent, and without cookies.
OpenAI
Text and image generation in AI Studio.
Claude · Claude Code
Claude and Claude Code, in the development workflow. Not part of how customer data is processed.

Certifications held by these providers are the providers’ own, not Winglark’s. The subprocessors page lists who processes data, for what, and where. Subprocessors

Security and trust

Security is designed in, and documented in public.

The Trust & Security Center describes each protection in detail. In short:

  • Each organisation’s data is isolated, and agencies can keep every client apart
  • Sign-in with Google, or a password stored with a strong one-way hash
  • Guest data encrypted in transit and at rest, contact details masked by role
  • Delivery reports verified by signature; unsigned or stale ones are refused
  • Production, staging and test environments kept apart
  • Every change tested before it is released
  • Exports of personal data and administrative actions recorded with a reason
Explore Trust & Security

Privacy and data principles

Privacy is part of the product, not a feature beside it.

Running an event means handling information about people: names, addresses, replies, sometimes dietary or access needs. Winglark is built on the view that this information should be collected only where an event needs it, seen only by the roles that need it, and kept out of everything else.

Guest data is stored in the EU and is not sent to AI, and measurement on this website waits for a visitor’s consent. The Privacy Policy sets out what is held, why, and how to have it returned or removed.

Read the Privacy PolicySee subprocessors

International product

Designed internationally from the beginning.

Winglark is written in five languages — not translated at the end, but built so that every screen, invitation and guest page has a language of its own.

  • English
  • Türkçe
  • Deutsch
  • Français
  • Español
  • Organisers choose the language of their workspace.
  • Each guest’s invitation and reply page can follow the guest’s own language.
  • This website is written natively in every one of the five.

Company direction

The operational infrastructure behind events — from the first invitation to the last guest leaving the venue.

That is Winglark’s long-term goal. We intend to reach it the way we have built so far: one dependable part at a time, released when it works and described only once it does.

Company information

Winglark at a glance.

For customers, partners, programmes and anyone verifying who we are.

Company
WinglarkIndependent event technology startup
Started
2026
Stage
Early Access
Operating from
Türkiye
European company structure
Planned in EstoniaThe Estonian company has not been registered yet. Its registration details will be published here once it is.
General contact
info@winglark.com
Security reports
Responsible disclosure

See it on your own event.

Winglark is in early access. Request access, a person reviews it, and an invitation to your workspace follows.

Request accessView pricing
Company — building the operating layer for events · Winglark