Who builds event67
event67 is a branded conference companion app for iOS, Android and the web, paired with an organizer console, billed per attendee who actually turns up. It is built by a small team in the open about its own limits, which is the part of this page worth reading.
Written and maintained by the people who build it
Every page on this site is written against one internal record of what the product does, kept in the same repository as the code, and the exclusions in it are as binding as the feature list. When a page here says event67 cannot do something, that has been checked against the product rather than hedged by a writer.
What event67 is, in two sentences
event67 gives an event organizer a branded app their attendees download under the organizer's own name, holding the schedule, the people, the questions, the photos and the notifications, plus a console to run all of it from. It is not a full event-management suite: it does not sell tickets, print badges, stream video or manage a call for papers, and the boundary is deliberate rather than a roadmap.
The positioning line is "Your conference, polished." What that means in practice is that we would rather do the attendee experience properly than do nine categories adequately.
The name is written event67, one word and lower case, and it is the same product whether you search it that way, as Event 67 with a space, or as Event67. There is no separate company behind any of those spellings.
Who builds it
event67 is built by Samar Swami and a small team. The product, the backend, the mobile app and the console are built in one place by people who also answer the support email, which is the arrangement that keeps the boundary lists on this site honest: it is difficult to overstate a feature to a stranger when you are the person who will be on the call when it does not do that.
There is no sales department. If you write to hello@event67.com you will be answered by somebody who can change the product.
We do not publish an advisory board, an investor list or a team page with stock photographs, because none of those would tell you anything true about whether the software will work at your event.
How we decide what to build
Three rules, applied consistently enough that you can predict our answer to a feature request.
First, we build the attendee experience and the organiser's side of it, and we do not build the commercial machinery around events. Registration, ticketing, payments, badges, contracts and budgets are all somebody else's product and they are all better at it than a bolt-on would be.
Second, we do not build a feature we cannot support properly at three in the afternoon on day two of somebody's conference. That rules out a great deal that would look good in a comparison table.
Third, when the honest answer is no, the answer is no on the website rather than in the demo. Every feature page on this site carries a section saying what that feature will not do, and the product inventory those pages are written from is the only permitted source of a product claim here.
What we deliberately do not build
This list is stable, published, and the same one our own writing is checked against. Nothing here is coming soon.
- Registration, ticketing and payments of any kind, including paid forms.
- Onsite badge printing and kiosks.
- Exhibitor lead retrieval, badge scanning and CRM sync.
- Interactive floor plans, venue maps and wayfinding.
- Virtual and hybrid streaming, breakout video, on-demand libraries and virtual booths.
- AI matchmaking and 1:1 meeting scheduling.
- Continuing-education credit tracking and certificates.
- Call for papers, abstract submission, peer review and speaker portals.
- Verifiable credential badges.
- Gamification: points, leaderboards and challenges.
One genuine gap rather than a scope decision: attendees have no in-app account deletion, and the deletion we do run today is not complete. Requests go through privacy@event67.com and the delete-account page, and they remove the attendee record without yet reaching the questions, photos and feedback held against the event. We name it here because it is the kind of thing a company hopes you do not notice, and the security page says exactly what does and does not happen.
How we write, and what we will not print
- Sources and dates
- Any factual claim about another company on this site carries a source link and the date it was checked. A claim we cannot source does not appear. "As of September 2026" beats "recently".
- Competitor content
- Plain-text names only, no logos, no lookalike styling, no superlatives in either direction, and a trademark and non-affiliation notice on every page that names anyone.
- Customer names
- We do not publish a customer name, logo or quote without written consent. One testimonial was removed at the customer's request on 1 September 2026 and it stays removed. There is no logo wall on this site and there will not be one.
- Ratings and reviews
- No star ratings, no invented review counts and no aggregate rating markup anywhere. If you want reviews, read them somewhere we do not control.
- Prices
- Every price on this site is generated from the same pricing code the product bills from, so the site cannot drift from the meter.
Reaching us
- hello@event67.com
- Anything commercial, and anything you would like the product to do.
- support@event67.com
- Something is not working, at an event or before one.
- privacy@event67.com
- Data access, export and deletion requests. Answered within 30 days.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Who is behind event67?
event67 is built by Samar Swami and a small team. The same people build the product and answer the support email, which is why the limits published on this site are specific rather than vague.
Do you name your customers?
No. We do not publish a customer name, logo or quote without written consent, and there is no logo wall on this site. One testimonial was removed at the customer's request on 1 September 2026 and has not been replaced with anything.
Why do your feature pages list what the product cannot do?
Because the alternative is a demo that ends with a missing-feature objection nobody saw coming. The categories we lose on are the ones where we would have wasted the buyer's afternoon, and publishing them is cheaper for both sides.
Are any of these features coming soon?
Nothing on the do-not-build list is planned. It is a scope decision rather than a backlog. The one item we describe as a gap rather than a decision is in-app account deletion for attendees, which is handled by email request today.
How do I ask for something?
Write to hello@event67.com. There is no sales department in the way, and the person who replies can change the product.
Keep reading
Ask us something specific
There is no sales department in the way, and the person who replies can change the product.