RingUps connects to four outside services today: Stripe for card payments, Resend for email, Supabase for the database and Anthropic for its two AI features. It publishes an iCal appointment feed and exports 30 report datasets to CSV. Every row in the table below carries its real status.
100 emails delivered in production through Resend, the most recent on 4 August 2026, each with a real message id on the row. That is the only outside service RingUps can point at a production log for.
Three status values only. Live means any store gets it. Live for the pilot store only means it is built and running but cannot be turned on for you yet, and the row says why. Not built means there is no code, no account and no date.
| Connection | What it does | Status |
|---|---|---|
| Resend | Carries every email RingUps sends, from the 12 customer templates. 100 messages delivered in production, most recently 4 August 2026, each with a real Resend message id stored on the row. Held messages are stored too, with a plain-English reason. | Live |
| Supabase | The database and file storage behind RingUps, in the ca-central-1 region. Your store's rows are scoped by the database itself rather than by the application, which is what makes one export endpoint safe to share across 30 report datasets. | Live |
| Anthropic | The two AI features: first drafts of training material, and gown attributes read from a photograph. Requires an Anthropic API key provisioned for your store. No key, no AI features, and the rest of RingUps is unaffected. | Live |
| iCal appointment feed | The appointment calendar as a subscribable feed, readable in Google Calendar, Apple Calendar, Outlook or anything else that reads iCal. Alterations fittings do not appear on it. | Live |
| CSV export | 30 report datasets download to CSV from one endpoint that runs the same query the report page just ran, so the file cannot disagree with the screen. Sales targets is the one report page with no CSV export yet. | Live |
| Public booking page | A booking page a bride reaches from your own website, showing your appointment types and opening hours. A full end-to-end booking has run on it: 12 slots offered, the booking confirmed, the row verified in the database afterwards. | Live |
| Stripe | Card payments taken inside RingUps. A Checkout Session, a signature-verified webhook, and ledger legs written when the webhook confirms the money. Shipped 17 July 2026. The Stripe client is single-org and throws for any organization other than the pilot store, so it cannot be turned on for a new store. Refunds never reach Stripe: RingUps writes the ledger entry and a person issues the card refund by hand in the Stripe dashboard. | Live for the pilot store only |
| Public API | There is none. No endpoint, no key to issue, no developer documentation. Nothing outside RingUps can read or write your data programmatically. Export is the only route out. | Not built |
| QuickBooks, Xero and other accounting packages | No connection of any kind. Accounting data leaves RingUps as a CSV file that a person imports or keys in. No live sync, no chart-of-accounts mapping, no journal entry pushed anywhere. | Not built |
| Card terminal and debit machine | RingUps does not read your terminal and does not reconcile against its batch totals. You take the card the way you take it now and record the payment against the order, which is what every store other than the pilot does. | Not built |
| Google Business Profile and review platforms | Nothing is posted to or read from Google. A review request from RingUps is an ordinary email like any other, and no review, rating or reply comes back into the system. | Not built |
| The Knot, WeddingWire and bridal directories | No connection. Enquiries arriving from a directory are entered the way any other enquiry is entered. | Not built |
| Scheduled or emailed report delivery | Reports are pull-only. You open the page, set the range, read it and export it. If a Monday number has to reach somebody, a person sends it. | Not built |
Four services do real work behind RingUps, and a full CSV export covers the rest of what a store needs to move data around. The six rows at the bottom are things a prospect might reasonably assume were there - we would rather you read them here than discover them in month two.
A short list is a security answer as much as a capability answer. The fewer outside services a system calls, the fewer places your brides' details can end up. These four are all of them.
Nothing else is called. No analytics vendor holds your bride list, no marketing platform syncs it, and no directory reads it, because none of those connections exist. What RingUps has not certified is stated on the security page, and it includes no SOC 2 and no PCI scope.
By exporting it, without asking us. RingUps has 30 export keys, one for each report dataset, and every store can take a full export of its own data. The export endpoint runs the same query the report page just ran, so the file and the screen cannot drift apart, and values beginning with an equals sign are neutralised so a bride's name cannot execute as a formula in a spreadsheet.
This is the part of the page we are least embarrassed about, because it is the part we tested from the other side. Moving Cande Bridal Boutique off Bridal Web Solutions meant living inside somebody else's export for weeks. Their sales tax export, their payments export and their line data gave three different answers on a single order. Their category screen said 655 units in stock while their own inventory export said 506. What survives that experience is a strong opinion about exports that disagree with the screen.
The other half of portability is being able to reverse a mistake. Imports into RingUps are reversible in one click, and every imported row is idempotent on the combination of organization, source and source reference, so re-running an import does not double it.
The hub as a layout, not a screenshot. 28 report pages sit under these groups and 30 datasets export, including the one row above that does not.
RingUps has no public API. Neither does Bridal Web Solutions. The difference is which of us tells you before you sign.
By file, not by sync. You open the report, set the month, export the CSV, and your bookkeeper imports it or keys the summary in. RingUps does not push a journal entry to QuickBooks, Xero or Sage, does not hold a mapping to your chart of accounts, and does not know what your account codes are called.
There is a reason worth stating rather than hiding. A bridal month end is not mostly a transfer problem, it is a recognition problem: a deposit taken in March is a liability until a gown is handed over in November. RingUps posts that deposit to deferred revenue when it is taken and recognizes the revenue on the pickup date, so the figures on the export are already on the right side of that line. Getting the right number out matters more than the number arriving automatically, and only one of those two is built.
Two honest caveats before your accountant asks. Deferred-revenue history does not exist for orders that came from your old system, because the import loaded orders and payments but never replayed the ledger, so those tiles read zero for imported history. And there is no multi-province or multi-state tax: every open rate matching a line's tax code applies to every order.
The Stripe row above is one line of a longer answer. That page has the whole ledger story, including what happens on a cancellation and why a deposit is not March income.
Read about paymentsThe 30 export keys in detail: which 28 pages produce them, what each one covers, and which reports read as near-empty on imported history rather than pretending otherwise.
See the reportsWhat the Resend connection carries: the 12 customer templates, and the suppression log with a reason per held message.
See what gets sentNo. RingUps has no public API today. There is no documented endpoint, no key to issue and no developer documentation, so nothing outside RingUps can read or write your data programmatically. What exists instead is export: 30 report datasets download as CSV, and a store can take a full export of its own data at any time. We say this plainly because we say the same thing about Bridal Web Solutions, which has no API either.
No. RingUps has no accounting integration of any kind, to QuickBooks, Xero, Sage or anything else. Accounting data leaves RingUps as a CSV file that a person imports or keys into the books. There is no live sync, no chart-of-accounts mapping and no journal entry pushed anywhere. If a live accounting sync is a requirement for you, RingUps does not meet it today.
Only the pilot store can. The Stripe connection is built end to end, with a Checkout Session, a signature-verified webhook and ledger legs written when the webhook confirms the money, and it shipped on 17 July 2026 for Cande Bridal Boutique. The Stripe client in RingUps is single-org and throws an error for any other organization, because opening it up needs Stripe Connect, which needs a legal entity that does not exist yet. Every other store keeps its own processor and records the payment against the order in RingUps.
Yes. RingUps publishes an iCal feed of the appointment calendar, which any calendar application that reads iCal can subscribe to. One thing is missing from it and you should know before you rely on it: alterations fittings do not appear on the appointment calendar or in the iCal feed. A fitting and an Alterations-department appointment are two separate records that do not sync, so a store running both looks in two places.
Name the thing your store depends on and we will tell you which of the three statuses it has, on the call, without a maybe. A store asking is how something moves off the bottom of that table.