Online and digital campaign infrastructure
The layer underneath everything else — domains, hosting, deployment, measurement and the route from a draft to a published page — set up so the operation stays online, stays fast, and belongs to the organisation.
What this covers.
Every engagement is scoped in writing before it is built. These are the parts of it this discipline is responsible for.
Domains and DNS
Registration, records and renewals held in accounts the organisation controls, with the expiry dates written down somewhere other than one inbox.
Hosting and deployment
A deployment process where every change is reviewed on a preview URL before it is live, and can be rolled back after it is.
Measurement
Analytics configured against the questions the office actually asks, collecting what is needed for those and not more.
Content pipeline
A repeatable route from a draft in the office to a published page that does not require a developer in the middle.
Monitoring
Alerts when something stops responding, rather than a phone call from the one person who noticed.
Access and handover
Accounts, credentials and ownership documented, and held by the organisation from the day they are created.
Built for a situation, not a side.
Organisations whose domain, hosting and analytics are spread across accounts nobody can fully list.
Offices that need a site to stay up during the weeks when it matters most.
Teams inheriting infrastructure somebody else set up and nobody documented.
How it is built.
Ownership starts with the client
Every account is created in the organisation's name. Handover is the default state, not something arranged at the end.
Previewed, then promoted
Changes are deployed to a preview URL and read there. The live domain only ever receives something that has already been looked at.
Automated checks before release
Lint, typecheck, contrast and a production build run on every change, so a release is blocked by a machine rather than by a reviewer's attention.
Documented, in writing
What runs where, who owns it and what renews when — recorded so the next person does not have to reconstruct it.
Categories of tooling, not credentials. The final choice is made per project and recorded in the scope.
What we will not build.
We build infrastructure for political work. That is not the same as building machinery for political manipulation, and the difference is written down rather than assumed.
Measurement, not surveillance
Analytics are configured to answer questions about the site — what is read, what is slow, what is broken. We do not build individual-level tracking of visitors, cross-site identity graphs, or data collection whose purpose is to profile a person.
Consent first
Outreach runs on contacts who have opted in, through each channel's own approved mechanism, with an opt-out that works. We do not build around a platform's consent rules.
No profiling, no persuasion engineering
We do not build voter scoring, psychographic profiling, micro-targeted persuasion, or any system whose purpose is to change how a person votes without their knowing why they are being shown it.
A person in the loop
Anything an AI system produces for an audience outside the organisation is reviewed by a person before it is published or sent. That review is part of the software, not a rule somebody has to remember.
Nothing invented
No claim, figure, endorsement or credential goes live unless the organisation can evidence it. The rule applies to this website as strictly as it applies to yours.
Tell us what it has to do.
Describe what you are running and what this has to handle. We will tell you what we would build, what it would take, and what we would leave out.
Rajasthan first, India next.