How Kopimore Works — Plain English Guide

This page explains every technical piece of Kopimore in plain language — no coding knowledge required. Think of it as a map of all the moving parts, what they do, and what would break if one stopped working.

Kopimore is made up of three separate websites that all work together:

All three are static HTML files hosted on SiteGround and deployed automatically from GitHub whenever a change is made. Behind the scenes, they all talk to the same Supabase database and the same set of edge functions.

Supabase is the database. Think of it as a giant, cloud-based spreadsheet that the entire application reads from and writes to. Every time a customer creates an account, configures an alert, connects their CRM, or a visitor gets identified — that information goes into Supabase.

If Supabase goes down: Customers can't log in, the dashboard shows no data, payments stop processing, and no visitor data is saved. It is the most critical dependency in the entire stack.

Edge functions are small programs that run in the cloud and do specific jobs when called upon. Think of each one as a specialist on staff — you call them up, they do one task, then hang up. They live inside Supabase and run on demand. Kopimore has the following edge functions:

Stripe is the payments company. Kopimore never sees or stores a customer's credit card number — that's handled entirely by Stripe's secure checkout page. Kopimore just tells Stripe "this customer wants to subscribe to the Growth plan" and Stripe handles the rest: collecting the card, charging it monthly, managing refunds, and sending receipts.

Currently blocked: The Stripe sandbox keys must be swapped to production keys before any real customer can pay. This requires logging into the Stripe dashboard, getting the live keys, and adding them to Supabase Secrets.

Kopimore's core product promise is "identify anonymous website visitors." AudienceLab is the company that actually makes that identification possible. They maintain a database of 200+ million company profiles matched to IP address ranges. When Kopimore asks "who visited this website?", AudienceLab cross-references the visitor's IP address against their database and returns the company name, industry, employee count, and other firmographic details.

Critical dependency: Without the DATAMOON_WEBHOOK_SECRET secret set in Supabase, no visitor data appears anywhere in the customer portal. The API key must be obtained from the AudienceLab account and added before launch.

Every Kopimore customer installs a small snippet of code on their website (similar to how you'd install Google Analytics). This code is the pixel.js script. When a real visitor loads that customer's website, pixel.js silently runs in the background, records the visit (page URL, session duration, referral source, screen size, UTM parameters), and sends all of that information to Kopimore's servers. This is what creates the raw visitor log that AudienceLab then enriches with company data.

Resend is the email delivery service. When Kopimore needs to send an email (welcome email after signup, payment confirmation, team invite, weekly report), it uses Resend to actually deliver those emails to the recipient's inbox. Resend ensures emails don't end up in spam, handles retries if delivery fails, and provides delivery reports.

Resend has been configured to send from @kopimore.com addresses with domain verification already completed. The 9 email templates (welcome, alert, invite, digest, payment confirmed/failed, trial expiry, support ticket, suspension) are built into the send-email edge function.

If Resend goes down: Customers still get access, payments still work, and visitor data still flows — but all email notifications stop. New signups won't get a welcome email, payment failures won't send a warning, and team invites won't arrive.

Kopimore lets customers automatically push their identified visitors into their existing CRM (Customer Relationship Management) tool — the software they use to track sales leads. Three CRMs are supported:

Note: HubSpot requires one additional setup step before launch — the OAuth redirect URL in the HubSpot developer app must be updated from a localhost URL to https://app.kopimore.com/crm.html. Until this is done, HubSpot connections will fail.

A domain name like kopimore.com is like the address on an envelope. DNS (Domain Name System) is the postal service that figures out which server to actually deliver requests to. Kopimore uses several subdomains, each pointing to a different server or service:

Authentication is the system that checks who you are when you log in. Kopimore uses Supabase Auth, which handles this entirely. Here's exactly what happens when a customer logs in:

Passwords are never stored in readable form — not even in the database. If a password is forgotten, Supabase sends a reset email and generates a new password hash. Even Kopimore employees cannot see a customer's password.

An API key is like a password that lets one service talk to another. Kopimore's edge functions need several of these to communicate with external services. They're stored in Supabase's "Secrets" vault — a secure area separate from the code, so they can't accidentally be published to GitHub. The key secrets are:

Secrets are managed at: Supabase Dashboard → Project Settings → Edge Functions → Secrets. Never paste secrets into code files or send them over email or Slack — they should only ever live in the Secrets vault.