

Pipsy is SOC 2 Type 2 compliant — and Type 2 isn't a one-time check. It's evidence that the security, availability, and confidentiality controls protecting your data and your buyers' have been in place and operating effectively over time.
JWT-based auth with role-aware permissions, plus OAuth 2.0 + PKCE for any MCP or third-party client integrations.
The GraphQL API restricts data by builder, property, and individual field — so partners only ever see what they're entitled to see.
Every authentication event, API call, document access, and email send is captured with structured logging for full traceability.
Each client lives in its own dedicated database — not a shared schema with a tenant ID column. Complete physical separation of data.
HTTPS everywhere, parameterized queries, input sanitization, and CloudFront signed URLs for time-limited access to private documents.
Tiered rate limits across auth, public, and standard endpoints. Automated AWS-managed backups with documented disaster recovery procedures.
Pipsy ships a production GraphQL API that exposes the entire dataset behind your communities — lots, properties, sales, buyers, traffic, floorplans, neighborhoods, sections, lot types, area features, incentives, salespeople, realtors, contracts, and dozens more. It's the same data layer that powers Pipsy's own dashboards, the MCP server, and your public-facing applications — so whether you're building a custom phone app, hooking into your data warehouse, or backing your executive dashboards with real-time data, you're working off one consistent source of truth.
Schema-typed, version-controlled, with field-level access controls that respect your builder and property partitioning. BDX-formatted XML feeds remain available for partners who need them.
Public schema for inventory and marketing data; authenticated schema for sales, buyer, and traffic records behind a JWT.
Restrict what each API key can see down to the individual field — partners get exactly what they're entitled to, nothing more.
The same API powers Pipsy's product, the MCP server, and every partner integration. If it works for us, it works for you.
BDX-formatted XML output is fully maintained for the partners and tools that still speak that language.
query
lots(property: "Dubay Pines", lotType: "60'") {
id
address
price
status
builder {
name
}
floorplan {
name sqft beds baths
}
}
→ 147 lots returned in 12ms

Pipsy extends its capabilities through strategic partnerships, bringing best-in-class solutions directly into your workflow.
Transform weekly drone scans into visual intelligence. Integrate TraceAir's aerial imagery with Pipsy's data platform for unprecedented site visibility, automated construction statuses, and stakeholder communication.
Visit TraceAirBridge home purchase and community engagement. Automatically onboard buyers to their community's digital ecosystem with instant access to amenities, events, and neighbor connections.
Visit AlosantWhether you're operating in a Microsoft or Linux based stack, Pipsy can communicate with your existing environment.
Through it's module-based system, Pipsy can be completely customized to the developers unique processes and procedures.
Pipsy is laser focused on the unique needs of master planned community developers.
Keep your existing CRM and ERP stack. Pipsy talks to the systems your team already uses to pull and push the data you require.
HubSpot
Lead push/pull, custom fields
Salesforce
Bidirectional sync
Dynamics 365
Lot & property sync
SmartSuite
Master plan & lot plan sync
Intacct
Accounting integration
Mailchimp
Email marketing
Zonda & CBAS
Market data feeds
TREC
Licensed realtor data
BDX Feeds
Builder inventory XML
TraceAir
Drone aerial intelligence
Alosant
Community engagement
… and many more
If it has an API, we can connect it to Pipsy