One integration. Every subscriber, verified by you.
Your service plugs into a Core Asset once, through a single adapter. From there the CRM & Ops platform, every Co-Foundry Labs venture and every licensee consumes it through the same governed interface, with tenant separation, credential security and usage metering handled before a request ever reaches you. Each subscriber stays responsible for its own compliance.
Where each partnership stands today
We list a partner by name once there is a working integration or a registration under way. Logos appear only with each partner's approval.
| Partner service | Core Asset | How customers connect | Status |
|---|---|---|---|
| TwilioVoice, SMS, phone numbers | Voice AI Agent · Messaging Gateway | Their own Twilio account today; through Co-Foundry Labs as ISV Reseller or Partner next | Registration in progress |
| WhatsApp Business PlatformCloud API | Messaging Gateway | Their own WhatsApp Business Account on the Cloud API | In build |
| Payment providersStripe and Razorpay first; Square, PayPal, UPI and RuPay through regional rails next | Payments | Their own provider account, with vendor-hosted checkout | In build |
| VAPI, ElevenLabsRealtime voice agents, text to speech | Voice AI Agent | Their own account today; ISV partnership candidates | Planned |
| TelegramBot API | Messaging Gateway | Direct integration | Planned |
| Email, POS and deliveryPostmark, SES, Clover, Toast, delivery networks | Email · POS · Delivery Network | To be set per provider | Planned |
Bring your own account
The customer registers their own account with you once per environment. We keep the credentials in a vault, never show them back, and set up your webhooks for them where your platform allows it.
Through Co-Foundry Labs
For customers without an account of their own, Co-Foundry Labs holds the partner relationship as an ISV, helps each customer complete its own registration and verification with you, and provisions numbers on the customer's behalf.
Your service plugs in once, at the adapter layer
Every Core Asset follows the same layered design. Clients never call your API directly, and your adapter never needs to know which product or venture is calling. That separation is what lets one integration serve many customers safely.
Every request is authenticated, tied to one subscriber and checked against that subscriber's access and plan before it goes anywhere near you.
Payments, messaging, voice AI, AI models and delivery. Clients name the provider and their connection; we translate the request to that provider's API. We never choose or switch providers for them.
The only place your API appears. Adding your service, or a new region of it, changes one adapter and nothing built on top.
Your webhooks are verified on the way in, events are signed on the way out, and usage is recorded per customer so it reconciles with your invoices.
We facilitate the services. Subscribers own their compliance.
Each subscriber uses your service under its own name and its own obligations. Co-Foundry Labs runs the integration securely and gives subscribers the tools to meet your rules; the subscriber is responsible for how it uses them. Every subscriber agreement sets out this split.
| Area | Co-Foundry Labs provides | The subscriber is responsible for |
|---|---|---|
| Every service | Credentials kept in a vault and never shown back; your webhooks verified; signed events; each subscriber kept separate; usage records | Its accounts and agreements with you, and complying with your terms and policies |
| Messaging | One interface for sending and receiving; template submission to you for review; delivery receipts; registered DLT details carried on India SMS | Opt-in and consent, opt-out handling, message content, the WhatsApp 24-hour window, DLT and 10DLC registration |
| Voice | Agents, calls and transcripts on the subscriber's chosen provider; number provisioning where we hold the ISV relationship | Call recording disclosure, permitted calling hours, consent to call, and what its AI agents say |
| Payments | Provider-hosted checkouts and payment links only; card numbers rejected; funds never pass through Co-Foundry Labs | Its merchant account and verification with you, refunds, disputes and tax |
Every customer stays separate, all the way down
One customer per request
Every request is tied to one customer. That customer's data, credentials and limits are kept apart from every other customer's.
Numbers, their choice
Customers bring their own business numbers or use platform default numbers we provision as an ISV. Co-Foundry Labs uses its own numbers for its own communication.
Data stays with the customer
Personal data is encrypted, kept for the customer's retention period, exportable and deletable on request, and held in the region the customer requires.
No content in logs
Monitoring records which customer and partner a request involved, never message or payment content.
Shared or packaged
Most customers use our shared cloud service. Regulated customers can run the same capability inside their own cloud or region.
Metered per customer
Every billable action records vendor cost and our cost per customer, so usage reconciles cleanly against your invoices.
From agreement to first live customer
Each customer environment runs in mock, sandbox or live mode, and nothing moves to live until it has passed in sandbox.
- Agreement and registrationPartner terms signed; Co-Foundry Labs registered as ISV or platform partner and business profile verified.
- Adapter buildWe build one adapter for your service and test it against our standard partner test suite.
- MockEvery integration starts in mock mode: documented responses and simulated webhooks, so customers can build before they have an account with you.
- SandboxTested end to end with your test credentials, then conformance and load tested before anything goes live.
- Subscriber registrationEach subscriber completes its own sender registration and business verification with you. We facilitate it and provision numbers where we hold the ISV relationship.
- LiveSwitched on environment by environment, customer by customer, and monitored against service targets.
One accountable partner across the portfolio
Co-Foundry Labs owns the integration, the support escalation and the roadmap with you, whichever venture or licensee a request came from.
- Monitoring and service targets for every capability
- Failed events held and replayed after an outage
- Automatic back-off that protects your rate limits
Volume without one-off integrations
Every new venture or licensee that needs your capability reaches you through the adapter you already certified.
- Subscribers verified by you before their first live traffic
- Clean usage records per customer
- A single technical and commercial contact
Partnerships: info@co-foundrylabs.com