The essential factors [1] are: * There are types of software that are politics-specific, and therefore do not exist until a party pays for it to be made. * Po

The essential factors [1] are: * There are types of software that are politics-specific, and therefore do not exist until a party pays for it to be made. * Politics is a zero-sum game: if you're funding software (either institutionally, or by being a tech worker who works below market wage For The Cause), you don't want it to be used by your political opponents. So commodity stuff that already exists is bipartisan. Any application that is specific to political campaigning is highly partisan. [1] There's also a secondary issue of data security for cloud products; parties maintain extensive voter files with things like past voting history, up-to-date contact information, and past contacts [1a]. They do not want this information falling into the hands of the opposing party, and so don't want their data touching any organization that might potentially have cross-partisan ties, or godforbid might have cotenancy for D and R data. [1a] This is basically the king of all CRMs, and these days they might be able to reimplement it as a bunch of plugins on top of a commercial provider like Salesforce, but those only became available relatively recently, data migration would be nontrivial, and there's a substantial amount of politics-specific functionality that would need to be rewritten as plugins.