Industries

Where the constraints are the design

Every sector has one rule that decides the architecture. These are the five whose rules we build around, and what each one actually changes.

Where most of our own products live

Social media

The ruleplatform rules you do not control, and posts you cannot take back

Most of what we have built ourselves lives here. Every platform sets its own formats, limits, rate limits and app review, and can change them without notice: Clepora publishes to nine of them, with YouTube and TikTok approved and Meta still in review. A post cannot be unsent, so Newsroom holds every one of its platform posts for a person to approve, and uses credited publisher photographs rather than generated ones. Whinchat keeps chat and calls working on weak networks, and Fact Studio turns researched facts into vertical reels, every fact checked against its sources.

Healthcare

The ruleHIPAA, and a records system nobody is allowed to break

Protected health information changes what "done" means. Access has to be scoped per patient and per role, every read has to be attributable months later, and the retention rules are law rather than preference. We build the audit trail as part of the feature, because reconstructing one after the fact is how projects lose a year.

Financial services

The rulemoney movement, KYC, and adversaries with a budget

Anything that moves money inherits obligations: identity verification, sanctions screening, dispute handling, and an accounting trail that survives a reconciliation. We have built escrow with verification gates and OFAC SDN screening for our own marketplace, which is why we can talk about the parts that are genuinely hard rather than the parts that demo well.

Public sector

The ruleNIST control families and evidence an assessor will accept

Government buyers do not want a promise that a system is secure; they want the control mapped, implemented, and evidenced. Building toward NIST SP 800-53 from the first commit costs a fraction of retrofitting it, and the test suite doubles as the evidence package.

A note on how we talk about this. Pontelon is a new firm. These are the domains our engineering is built for and the regulations we design against — not a list of clients we have shipped for. When we have delivered client work we will publish it as such, named and with permission.

Your sector not here?

Tell us the rule that decides your architecture.

Talk to us about your domain