What is Romulus?
Romulus combines the tools campaigns and elected officials normally buy from four or five separate vendors — a voter file, a canvassing app, a donor CRM, a communications suite, and a constituent-services system — into a single application backed by a single database. One tool, one login, one place your data lives.
A few things it isn't: it isn't a replacement for vendor voter files (you bring the file in from your state party, a commercial vendor, or the secretary of state, and Romulus indexes and annotates it), and it isn't an ad-buying platform (it exports audiences formatted for the platforms; you run the buys there).
See the features tour for what each module does.
Getting started
Log in with the email your admin used when adding you. If your organization uses Microsoft single sign-on you'll see that button too; if two-factor is enabled, a 6-digit authenticator code follows your password. You land on the Home dashboard — KPI cards, activity charts, leaderboards, the Action Center, and the next election — all draggable and toggleable, saved per browser, so each user can have their own view.
The tab bar shows only what your campaign has enabled and your role allows: typically Voters, Field, Fundraising, Communications, Volunteers, Analytics, Operations, and Rosie. If a tab you expect is missing, ask your admin about your permissions. Members of multiple campaigns get a campaign selector — each login is scoped to one campaign's data.
Most edits save automatically — voter notes and engagement save when you click away, drafts auto-save as you type, and contact events log instantly — with a confirmation toast on every save. From your avatar you can change your password, set up two-factor, register a passkey, and pick a theme.
Romulus vs. Numa
Romulus is for campaigns — candidate committees, ballot committees, and party organizations: voter contact, field, fundraising, comms, volunteers, GOTV. The officeholder side — casework, legislative tracking, district intelligence, constituent communications, public surfaces — lives in Numa, our platform for sitting electeds.
They're separate products because the compliance regimes differ: campaign data sits under FEC and state campaign-finance rules; office data sits under FOIA and public-records statutes, plus a strict no-electioneering line. The separation is physical — nothing crosses between the two, and the only shared data is the voter file itself.
An incumbent running for re-election can work in both — Romulus for the campaign, Numa for the office — and neither login grants access to the other side. The office side is documented in the Numa docs.
Security & privacy
Voter records, donor histories, and casework are sensitive, and the platform layers its defenses accordingly: revocable sessions in HTTP-only cookies, memory-hard password hashing, optional two-factor and passkeys (enforceable per campaign), Microsoft SSO, CSRF protection on every mutation, strict security headers, and rate limiting on login and API traffic.
Access is governed by custom roles over granular permissions, feature flags hide entire modules server-side, and every sensitive action lands in an immutable audit log — actor, IP, category, detail. AI requests are logged separately with provider and model, and inbound webhooks (WinRed, ActBlue, Mailgun, Stripe) are HMAC-verified and logged in full.
Your data stays yours: full backups are checksummed and downloadable with configurable retention, voter snapshots capture point-in-time copies of the file you can restore from, everything exports to CSV, and public surfaces are strictly opt-in. Canvasser GPS pings prune after 7 days; audit and AI logs after 90 by default.
YOUR PART
Romulus enforces the platform-side rules, but compliance stays with you: review FEC and state filings with counsel, confirm SMS and email consent before bulk sends, and honor cross-channel opt-outs.