Relic

The Clipboard Is the Most Underrated System of Record in Cross-Border E-Commerce

Cross-border sellers run their businesses on fragments. A supplier’s WeChat ID copied from a WhatsApp thread. A tracking number lifted from a 17TRACK page. An ASIN pulled out of a Helium 10 export. A VAT number pasted from an accountant’s email into a Shopify settings field. None of it lives anywhere durable. It lives in the clipboard, and the clipboard is where it dies. That’s why Relic, a copy-vault tool launched by Jordan Gibbs, is more relevant to operators than its consumer-app framing suggests. The pitch is simple: everything you copy is saved, synced, searchable, and private. The implication for anyone juggling supplier quotes across three time zones is less simple.

What Relic Actually Solves (and What It Replaces)

The maker’s own framing is refreshingly honest: he built it because he was tired of emailing himself stuff, or sending himself Slack messages, then scrolling through dozens of unrelated messages to find a link he needed a week later. That’s the real workflow most sellers have — a graveyard of self-DMs, “Notes” app entries, and starred Slack messages that nobody ever revisits.

Relic attacks that with four concrete mechanics:

• Clipboard capture with cross-device sync across Windows, Linux, Mac, iPhone, and Android, so the thing you copied on your laptop at 2 a.m. is already on your phone when the supplier replies at 9 a.m.
• Semantic and vector search, which means you can query by meaning rather than exact string match. The maker’s example is a natural-language date filter like “github repo from last month” that auto-applies a time filter.
• On-device AI classification that auto-titles and tags entries unless you override it manually.
• A CLI so agents can read and write to the vault, plus full self-hosting and open source.

The privacy posture is explicit: nothing leaves the machine unencrypted, and self-hosting is free. That last point matters more for cross-border operators than for the average Product Hunt upvoter, and I’ll get to why.

Where this sits versus what you’re probably already using

If you’re a seller, your current stack for this problem is probably one of four things, and none of them are good:

1. Native OS clipboard history — Windows Clipboard History or macOS’s paste stack. Free, local, but shallow: no sync, no semantic search, and it forgets everything on reboot by default.
2. A note app like Notion or Obsidian — great for structured knowledge, terrible for capture friction. You have to decide to save something, which is exactly the moment you won’t.
3. A password manager’s secure notes — wrong tool, wrong shape, and as one commenter on the launch asked directly, it’s unclear whether Relic skips whatever a password manager drops on the clipboard or whether you prune that yourself. The maker didn’t answer that in the thread, and it’s a real gap.
4. Slack self-DMs or Notion quick capture — the exact behavior Relic was built to kill.

The closest direct competitors in the clipboard-manager category are Paste on Apple platforms and Raycast’s clipboard history on Mac. Both are excellent and both are platform-locked in ways Relic explicitly isn’t. The maker’s own claim in the comments is that existing tools “either didn’t have true cross-platform support or weren’t secure” — that’s a positioning statement, not a benchmark, but it’s the right axis to compete on.

Why Amazon Sellers Should Care More Than Shopify Ones

Here’s my judgment call, and it’s the part of this essay that isn’t in the source material.

A Shopify DTC operator lives inside one or two tools. Their product data, orders, and customer records are all in the admin. The clipboard is a convenience.

An Amazon FBA seller lives in at least six surfaces that don’t talk to each other: Seller Central for listings and cases, a supplier’s email or WeChat for POs, a freight forwarder’s portal for shipments, Helium 10 or Jungle Scout for research, a spreadsheet for unit economics, and a separate tool for TikTok Shop or Temu if they’ve diversified. Every one of those handoffs is a copy-paste. Every copy-paste is a place where a SKU gets fat-fingered, a tracking number gets lost, or a supplier’s quote disappears into a Slack scroll.

That’s the asymmetry. The more fragmented your channel mix, the more value a clipboard vault delivers — and cross-border sellers are the most fragmented cohort in e-commerce by default, because they’re also spanning languages, currencies, and compliance regimes.

The compliance angle nobody on Product Hunt mentioned

Cross-border sellers handle data that has real regulatory weight: supplier bank details, customer PII in returns notes, VAT and IOSS numbers, customs declarations. The default behavior in most seller teams is to paste that into whatever’s convenient — a Google Doc, a Slack channel, a WhatsApp group. That’s a GDPR and CCPA exposure that most operators don’t think about until an audit.

Relic’s on-device classification and encrypted sync are, in that light, not a privacy-nerd feature. They’re a lightweight compliance control. If the clipboard is where sensitive data transits, then a clipboard tool that keeps data local and encrypted is doing work your DLP policy probably isn’t. I’d want to see the encryption model documented before I’d stake a compliance claim on it — “nothing leaves your computer unencrypted” is a good sentence, not a spec — but the direction is right.

What Cross-Border Sellers Can Borrow From This

Strip away the product and there’s a transferable operating principle here that’s worth more than the tool: capture should be a side effect of work, not a separate task.

Most seller teams run their knowledge management backwards. They do the work, then at some point they try to document it — build the SOP, populate the wiki, tag the Notion page. That documentation step is where institutional knowledge goes to die, because nobody does it under deadline pressure.

Relic’s design inverts that. You don’t decide to save something. You copy it, and it’s saved. The classification is automatic. The retrieval is semantic. The only human effort is the query.

Three ways to apply that principle even if you never install Relic:

• Audit your copy-paste surface area. For one week, notice every time you move data between two tools. That list is your integration backlog, ranked by frequency.
• Stop treating Slack self-DMs as storage. If your supplier contacts, tracking numbers, or case IDs live in a self-DM thread, you have a single point of failure with no search and no backup.
• Give your VA or ops hire a shared vault, not a shared spreadsheet. The spreadsheet is where data goes to become stale. A searchable, timestamped capture log is closer to an audit trail.

The CLI point deserves a separate mention, because it’s the most forward-looking thing in the launch. If your agents — sourcing scrapers, listing optimizers, repricing bots — can read and write to a shared vault, you’ve got the beginnings of a memory layer for automation. That’s a bigger deal than clipboard history, and it’s the thread I’d pull on.

Where the math breaks

Two honest caveats.

First, sync is a liability as much as a feature. A clipboard that syncs across five devices is a clipboard that can leak across five devices. The maker’s answer is encryption and self-hosting, which is the right answer, but self-hosting is a skill most seller teams don’t have in-house. If you’re not going to self-host, you’re trusting a hosted sync layer with everything you’ve ever copied — including, potentially, the password-manager entries one commenter flagged. That question is unanswered in the thread and it’s the first thing I’d want clarified.

Second, on-device AI classification is only as good as the model on the device. Auto-tagging is genuinely useful when it works and actively harmful when it mislabels in ways you don’t notice. For a seller with thousands of SKUs, a mis-tagged supplier quote is worse than an untagged one, because you’ll trust it.

What I’d Watch / Test Next

This week, do three things.

One: install Relic on two devices — your work laptop and your phone — and run it for five working days on nothing but supplier and logistics copy-paste. Don’t change any other behavior. At the end of the week, search the vault for a tracking number and a supplier quote you know you handled. If retrieval is faster than your current method, you have your answer.

Two: before you put anything sensitive in it, get a straight answer on password-manager clipboard behavior and on the encryption model for hosted sync. The maker is active in the launch thread and open source means you or a technical hire can read the code. Don’t take the marketing line as a spec.

Three: if you run any automation — repricing, listing generation, sourcing scrapers — prototype the CLI as a shared memory layer for one agent. That’s the use case with the highest ceiling and the least competition. Clipboard history is a commodity. An agent-accessible, encrypted, searchable vault of everything your business has ever copied is not.

The bigger lesson stands regardless of whether Relic wins: your clipboard is a system of record whether you treat it like one or not. The sellers who start treating it like one will have a quiet, compounding advantage over the ones still scrolling up through Slack.