Where You Run TapTech

TagsPortalCoreHow TapTech works ↓

Every tag, every Portal and everyone who said yes, on one record that belongs to you rather than to a platform.

Self serve is a beta for selected Base, Studio and Label clients from the fourth quarter of 2026, and the full platform launches to selected clients in 2027.

Core: Home

Three Parts. One Record That Compounds.

TapTech is the Tags people tap, the Portal a tap opens, and Core, where you run all of it.

One Login, One Audience, One Record

Core shows only the systems you use. They share the same audience and the same record, so adding one later needs no new setup.

  1. What needs you today: live numbers, what changed, and anything waiting on a decision.

    In the docs ↗
    Core, Home
Core, Home

Everything Core Does

Each system has its own page: what it does, the real screen, and where it is already in use.

All features →

From Box to Live

Five steps, from the box arriving to taps landing in Core. After that, you change the page, not the tag.

  1. Core, the Tags list with a new batch waiting to be claimed
    01 · Day one

    The box arrives

    Tags come programmed and locked, with the batch number on the box.

  2. Core, a batch of 1,200 tags just claimed
    02 · Two minutes

    Claim the batch

    Enter the batch number and the whole shipment is yours in Core.

  3. Core, choosing the Portal a batch opens
    03 · One minute

    Point it at a Portal

    Choose the Portal, or a page inside it, that this batch should open.

  4. Core, a batch confirmed live
    04 · From then on

    Live, and changeable

    Repoint a batch, switch one tag off or change the page mid event, without touching a tag.

  5. Core, Insights with taps by place and time
    05 · As it happens

    Watch it land

    Taps by place and time, who said yes and who came back, on one record that belongs to you.

Integrations

Dark tiles are DEPARTMNT's own tools, built into TapTech. Filled tiles are live; outlined ones are in beta or in build.

Tickets and wallets

  • TicketingPresale, guest lists, refunds, voids and an offline door, run from CoreBuilt in
  • Apple WalletTickets saved to the fan's iPhoneLive
  • Google WalletThe same, for AndroidIn build

Payments and commerce

  • CommerceProducts, memberships and drops sold from the Portal, run from CoreBuilt in
  • StripePayments and payouts through Stripe Connect. You are the merchant of recordLive

Music and media

  • Music playerReleases, demos and streaming links, played inside the PortalBuilt in
  • SpotifyRelease and artist embeds in the PortalLive
  • Apple MusicStreaming links from the Music playerLive
  • YouTube MusicStreaming links from the Music playerLive
  • TidalStreaming links from the Music playerLive
  • DeezerStreaming links from the Music playerLive
  • Official ChartsTagged physical releases that can count towards the chartsBeta

Messaging and social

  • Fan VoiceCommunity chat, a member directory and group chats inside the PortalIn build
  • Web pushLock screen messages to fans who said yes, with no appLive
  • EmailConfirmations and tap to email, sent through ResendLive

CRM and email marketing

  • Core CRMFans, segments and campaigns, with consent kept on every recordBuilt in

Doors and access

  • Door scanners and readersOur own scanners and readers, validating tickets offline at the doorBuilt in
  • PaxtonWorks alongside existing Paxton Net2 doorsLive
  • UniFi AccessDoors that open with Core credentials and bookingsIn build

Data and automation

  • CSV exportConsent filtered and watermarkedLive
  • CRM exportConsented contacts out to your CRM, under a DPAIn build
Coming next · 22 planned integrations

Tickets and wallets

  • DICELink out to DICE events, or bring their data into CorePlanned
  • EventbriteLink out to Eventbrite events, or bring their data into CorePlanned
  • TicketmasterLink out to Ticketmaster events, or bring their data into CorePlanned
  • BandsintownTour dates pulled into the PortalPlanned
  • SongkickTour dates pulled into the PortalPlanned

Payments and commerce

  • ShopifyProduct pages, member early access and Page LockPlanned
  • WooCommerceFor brands not on ShopifyPlanned
  • SquareMerch desks and in person salesPlanned

Music and media

  • YouTubeMusic video embedsPlanned

Messaging and social

  • SMSA text after a tapPlanned
  • WhatsAppMessages to fans who opt in, through the Business APIPlanned
  • InstagramVerified handles at sign up and story sharingPlanned

CRM and email marketing

  • HubSpotConsented contacts and lists synced to HubSpotPlanned
  • SalesforceConsented contacts synced to SalesforcePlanned
  • KlaviyoConsented contacts and events synced to KlaviyoPlanned
  • MailchimpConsented contacts synced to Mailchimp audiencesPlanned

Data and automation

  • API and webhooksYour record into your own systems, on Agency and NetworkPlanned
  • Google SheetsA live sheet of consented sign upsPlanned
  • AirtableSign ups and taps into an Airtable basePlanned
  • SegmentEvents into your CDP through SegmentPlanned
  • ZapierNo code automationsPlanned
  • MakeNo code automationsPlanned
Runs onSupabaseVercelCloudflareUpstashResendStripeSentry

Data and Consent

Presence, not behaviour. Core is consent first and records who was there, not what they did.

A tap records which tag, when, and the kind of device. Nothing about the person, until they choose to sign up.

  • Every consent is stored with its purpose, wording version and time. Withdrawal is honoured.
  • Exports are consent filtered and watermarked, with small cell suppression.
  • You are the controller and DEPARTMNT the processor, under UK GDPR.
  • Row level security in the database, fail closed defaults, and no card data stored or logged.

Core runs on Vercel, Supabase and Cloudflare, each independently certified to SOC 2 Type II and ISO 27001. Card payments are handled by Stripe, a PCI DSS Level 1 provider.

DEPARTMNT's own SOC 2 and ISO 27001 certifications are planned.

Security and compliance ↗
Latest · 2 Oct 2026Push notifications are available.Changelog →

Buying for a brand, a tour or a venue?