Accounts & Dependencies
v1.0 · OCT 2026
Accounts & Dependencies
v1.0 · OCT 2026
Ribbit.Deals connects to a handful of outside services, and a few things can only come from the founders and counsel. This page lists every one, in the order they’re needed. Tick items off as they’re done; ticks are saved in this browser.
Create: A business plan of 1Password, Bitwarden or similar, owned by The Pond Marketing Group, LLC, with a vault for Ribbit.Deals.
Why: Every account below needs a safe home for its logins and keys, and so does the app’s master key (APP_KEY, see the manual’s Backups section). Passwords must never travel by email or text.
Access for Jared: Invite Jared to the Ribbit.Deals vault.
Create: Confirm which registrar holds ribbit.deals and that it is registered to The Pond Marketing Group, LLC (not to an individual or an agency). Turn on auto-renew and registrar lock.
Why: The app’s permanent home (for example app.ribbit.deals) and its email sending both depend on it. Installed apps and push alerts are tied to the address, so it should change only once.
Access for Jared: Add Jared as a DNS user, or be ready to add DNS records he supplies.
Create: At least: support@ (members and owners write here), billing@ (statements and payment questions), and a sending address such as noreply@ for automatic emails.
Why: Password resets, statements and support all need a real address on the brand’s own domain. Today resets come from the test server.
Access for Jared: Share the addresses; Jared needs access only to the sending address’s settings.
Create: An account with a transactional email service (for example Postmark, Amazon SES or Resend), with ribbit.deals verified in it.
Why: Password-reset and account emails are sent straight from the web server today, which mail providers often send to spam. A sending service with the domain verified (SPF, DKIM and DMARC records, which Jared will supply) gets them delivered. The production build already supports these services; switching is configuration.
Access for Jared: Add Jared as a team member or developer; he’ll create the sending key himself.
Create: An account with the processor the founders choose (Stripe today, or another with hosted checkout and saved cards), in TPMG’s name: business details, EIN, bank account for payouts, and an owner’s identity check.
Why: Activation fees, monthly operations fees and performance fees are charged to businesses’ saved cards. Card details never touch Ribbit.Deals’ servers. The choice is still open in the spec’s Decision Log.
Access for Jared: Add Jared as a Developer (never share the owner login). Live mode is switched on only at launch.
Create: A GitHub organization for The Pond Marketing Group, LLC, with the Ribbit.Deals repository moved into it.
Why: The code is the company’s asset. Deployments run from the repository, so it should belong to the company, with Jared as a member.
Access for Jared: Invite Jared to the organization; he’ll help move the repository.
Create: An AWS account in TPMG’s name with billing set up (or the founders’ chosen host). This includes off-server storage for backups (for example an S3 bucket).
Why: The app runs on a test server today. Launch needs hosting the company owns, plus backups stored away from the server (see the manual’s Backups section).
Access for Jared: Create an access user for Jared with administrator rights for the setup, to be narrowed afterwards. Turn on multi-factor sign-in for every user.
Create: An account with a geocoding provider (for example Geoapify, Mapbox or Google Maps Platform).
Why: When a business adds a location, its address is turned into a map pin so members can be matched to nearby deals. Today this uses OpenStreetMap’s free public service, whose usage policy limits heavy and commercial use.
Access for Jared: Add Jared as a developer; he’ll create the key.
Create: Free or low-cost accounts with an uptime checker (for example UptimeRobot or Better Stack) and an error tracker (for example Sentry).
Why: So the team hears within minutes if the app goes down or a page starts failing, instead of from a business owner.
Access for Jared: Invite Jared; alerts go to support@ and Jared.
Counsel’s approved text, ready to publish in Admin → Agreements.
Shown at member sign-up and linked in the app. The privacy policy must match how the app actually uses data (for example: approximate location only for deal alerts).
Required before any drawing can go live (spec Open Question #6). Entry must stay free; Utah law is strict on games of chance.
Open in the spec (EULA §20).
Stripe or an alternative (Decision Log, OPEN). Needed before the payment account above.
Confirm in writing: launch in 2027 after the pre-launch campaign; Nov 27 stays the contracted completion date (Decision Log, REC).
Confirm dropping SMS alerts (Decision Log, REC).
Default count and any membership levels (Decision Log, OPEN).
Backlog items B4 to B8 in the spec: the watchlist, encouraging scans, nearby-member counts, the admin activity map, and ways to spend points. Which to take up, and whether through a change request.
Five to ten local businesses willing to try Ribbit.Deals first, with a contact for each (M4 beta onboarding).
What it is, its value, and who provides it, for the official rules.
Final logo files and any brand rules not yet supplied.
The email (and any phone number) members and owners should use.