Current platform foundation
FoundationGo owns the control plane, Python owns document intelligence, and the local development stack already includes the services needed to support future intake paths.
Integrations
Channels and handoffs, framed honestly.
The integration story matters because invoices arrive from different directions and verdicts need to reach the right people. PO Walls treats those surfaces as roadmap commitments with explicit status, not as vague promises.
Planned product integrations
PlannedWeb upload, public API ingestion, notifications, and Telegram intake sit in the MVP roadmap and are not being marketed as live yet.
Mailbox-native surfaces later
LaterGmail and Outlook add-on concepts are explicitly post-MVP and should stay in roadmap context only.
Planned MVP surfaces
Planned- Secure web upload for PDFs and images
- Notification routing across email, Slack, Telegram, and in-app channels
- Public API ingestion and result retrieval
Later-stage extensions
Later- Gmail add-on concept
- Outlook add-in concept
Use the roadmap status, not the buzzword list.
The integrations page is meant to show how PO Walls plans to connect with your workflow without pretending those surfaces are all live already.