Everything is an event
Linebundle is built on a single idea: every happening in the world is an event. A conference, a lecture, a clinic appointment, a product drop, a book club — if it happens, it’s an event. Everything else in the platform — spaces, contacts, places, attendees, materials — exists to give an event its context or to route it to the people who care about it. This is why Linebundle is a platform, not a single app. One primitive, shared everywhere, consumed in many forms.Every event has its W’s
An event is only complete when it answers a few simple questions. We call them the W’s. Linebundle’s job is to help organizers answer them well, and to present those answers clearly to everyone attending.
Where, Who, What, and When define the event. How is what makes it actionable — and it opens directly onto the platform’s other big idea: the bundle.
An event missing one of its core W’s is incomplete. Linebundle guides organizers toward filling them in, and surfaces them cleanly so attendees never have to guess.
The line and the bundle
The W’s say what makes an event complete. The bundle is how that complete event gets handed over. Like the W’s, the bundle is a high-level concept — not a feature or a builder tool. It’s the lens for everything an event carries with it.The line is the sequence of events running through a person’s life. The bundle is everything packaged with each event so the person can simply consume it. Together: Linebundle.An organizer doesn’t just announce an event — they bundle everything that event needs and hand the whole thing over, so the attendee has nothing left to figure out. The bundle wraps up:
- The W’s themselves — the where, who, what, and when, already answered.
- Resources & materials — the logistics that make How real. A concert with a location can carry transport, accommodation, and drinks; a study session carries the lecture docs, slides, and prep material; a conference carries maps, agendas, and parking passes. The attendee just taps and uses them.
- Ways to stay connected — notifications and updates the attendee can subscribe to, so changes reach them automatically.
- Transactions (growing over time) — capabilities like ticketing are part of the same bundle: everything needed to take part in the event, in one place.
The marketplace: where bundles get filled
A bundle is only as good as what goes into it — and much of that comes from outside Linebundle. The marketplace is the platform-wide capability that lets external infrastructure, providers, and data sources plug in, so anyone building an event can source what it needs without leaving the platform. Whatever they pull in becomes part of the event’s bundle. The marketplace is a core of the whole platform, not a Studio feature. It serves every surface — it just scales to who’s using it:- In Studio (powerful): an organizer can do calendar-wide research for the best date, hire artists, rent equipment, book venues, line up vendors, and sell tickets — the heavy operations behind running a concert or a school year.
- In Space (lightweight): a person creating a casual event to share with friends — a movie night, say — can pull in IMDb to attach the film’s details, or grab a place, a playlist, or a link, in a tap.
Automation: the primitive everything runs on
Underneath the platform sits one general-purpose engine: automation. It’s a simple trigger → condition → action model, and it’s not tied to events — it spans the whole platform. A rule can fire on almost anything that happens (an event published, an attendee’s status changing, a space created, a booking made, a contact added, or just a schedule), test it against rich boolean conditions (AND / OR / NOT, field comparisons, time windows), and then run actions: send a notification, call a webhook, hit the API, or invoke a third-party integration. Two things make this a cornerstone rather than a convenience feature:It powers managing events en masse
This is the real “power” behind Studio. Instead of touching events one by one, an organizer writes a rule once and it applies across every matching event, attendee, or space — automatically, at scale. Running a school year or a festival means setting the rules, not doing the repetitive work.
It's the substrate the AI relies on
Automation is the hands; the AI is the brain. The AI never touches platform data directly — every action it takes runs through the automation engine. That gives every AI action an audit trail, the user’s own permissions, and safe, idempotent execution by construction.
Every event has two sides
Notice that Who has two answers, always: the person who organizes the event, and the people who attend it. These two sides want very different things — so Linebundle serves them differently, on top of the same shared event.- Organizers need power and control: the ability to create and manage events at scale, with their team, and publish on their terms.
- Attendees need effortless consumption: to find an event, understand it at a glance, and act on it — wherever they already are.
Two roles: organize, then distribute
Everything in the platform reduces to two jobs done with one shared event:Studio organizes
The organizer’s operating system. Run an entire event — or an entire year of them — end to end and at scale: research, sourcing, planning, execution, and outcomes, with one team in one shared model. Studio is the authoring authority.
The platform distributes
The REST API, SDKs, webhooks, and notifications. Author and bundle an event once, then deliver it through whatever medium the attendee prefers — and let them consume it however they like.
Studio runs the whole event, end to end
Studio is not just a way to consolidate the five tools an organizer used to juggle. It’s purpose-built to orchestrate an entire undertaking at scale, on every front — from the first planning decision to the final outcome:- Research — do calendar-wide research across the public event landscape to pick the best date, avoid clashes, and find the right window.
- Sourcing — assemble everything the event needs: hire artists, rent equipment, book venues, line up vendors.
- Planning & execution — build timelines and schedules, coordinate the team with roles and permissions, and run the event as it happens.
- Outcomes — capture and distribute what comes after: results, grades, recordings, follow-ups.
- A music concert can be organized start to finish on the platform — research the best date, hire the artists, rent the equipment, book the venue, sell tickets, run the night, and follow up — all as one orchestrated event.
- A school can plan and execute its entire academic year together — the full timetable, semester exams, breaks, study materials shared through spaces (the org-tree), exam grading, and distribution of results — as one connected operation rather than dozens of disconnected ones.
Many mediums, one bundled event
Because the event is authored once and exposed through the platform, the same bundled event can reach attendees wherever they already are. The organizer picks the channels; the attendee picks how they consume:- Email & notifications — automations and announcements push the event and its updates over email, WhatsApp, or webhooks.
- A website — a third-party site uses the SDK or public API to display live events natively in their own product, with no duplicate data to maintain.
- A calendar subscription — published events need no account; an attendee simply subscribes the event into their own calendar.
- Integrations & AI agents — webhooks and the MCP server let other systems react to events automatically.
- The Space mobile app — Linebundle’s own first-party medium (below).
Studio’s job is to organize and bundle every event. The platform’s job is to distribute it across these mediums. The Space app is one of those mediums — the consumer chooses it the same way they’d choose to subscribe an event to their calendar — it just happens to be the one Linebundle built itself.
Space: the network-native medium
Space, the mobile app, is another distribution medium — but a deliberate one. It’s built first-party, specifically to take full advantage of the platform’s network capability in a way an email or a calendar subscription can’t. Space is about events and the communities a person cares about — nothing more administrative than that. People follow the spaces (communities, classes, teams, interests) that matter to them and see all of those events in one personal view: what’s live now, what’s coming up, the people they follow, and new communities to discover. Where email and website embeds distribute one organizer’s events to their own audience, Space turns the whole picture personal: it gathers every event from every community a person belongs to into one “what’s relevant to me right now” view — regardless of who runs those communities behind the scenes. That’s the flywheel: every new community that publishes events drops them into a graph that Space users already inhabit. Discovery and membership compound instead of fragmenting into isolated silos. The more organizers publish, the richer every attendee’s calendar becomes — and the richer the calendar, the more valuable it is for the next organizer to publish there. Email distributes to a list; Space distributes to a network.Organizations are administrative plumbing, not the consumer’s mental model. An organization is just the entity that owns a set of spaces and shares resources and permissions among its organizers (a company, a school, a promoter). The Space user never thinks in organizations — they think in events and communities. Spaces can still nest into one another (a festival space holding Stage A, Stage B, Vendor Area), but that structure serves the organizer; Space erases the org boundary so the person just sees everything that matters to them in one place.
In one paragraph
Linebundle treats everything as an event. An event is defined by its W’s — Where, Who, What, When, and How — and is incomplete without them. Each event then ships as a bundle: the organizer packages the W’s together with the event’s resources (transport, materials, refreshments, docs), its subscribable updates, and transactions like ticketing, then hands the whole thing over so the attendee can simply consume it. A platform-wide marketplace lets external infrastructure plug in so bundles can be filled from outside Linebundle — Studio uses it for heavy sourcing (hire artists, rent equipment, book venues, sell tickets, do calendar-wide date research), while a Space user pulls in something as simple as IMDb details for a movie night. Underneath it all runs one general-purpose automation primitive (trigger → condition → action) that powers managing events en masse, delivers the bundle’s notifications, executes marketplace integrations, and serves as the hands the AI brain acts through — every AI action runs through automation, so it inherits an audit trail and the user’s own permissions. Every event has two Whos: the organizer who creates it and the attendee who consumes it. Studio is the organizer’s operating system for running whole events — or a whole school year — end to end and at scale; the platform (API, SDKs, webhooks, notifications) distributes those bundled events through whatever medium the organizer chooses and the attendee prefers — email, a website embed, a calendar subscription, an AI agent, or the Space mobile app. Space is just one of those mediums, but a first-party one built to exploit the platform’s network: it gathers every event from every community a person follows into one personal social calendar — no matter which organization runs them behind the scenes (organizations are administrative plumbing, not what the app is about). It’s the line of events through a person’s life, each arriving as a complete bundle. That’s Linebundle.
What’s next?
Meet the building blocks
See how spaces, events, contacts, and places fit together in practice.
Build on the platform
Use the SDK to bring Linebundle events into your own product.