Reference library
Integrations
Every vendor and standard Wildo works with: the ERP and CRM a company runs, AI models, sign-in, email, payments, files and monitoring, each linked to what it does.
ERP and CRM systems of record
Declared once, then read in place, copied and kept current, written back or kept in two-way sync, with the owner of each field declared. Each is tested against a simulator faithful to its vendor’s protocol; runs against live tenants come next.
- SAP S/4HANAPartial
OData v4 and v2 services, read in place or copied.
- Salesforce
Records read with SOQL, copied and written back.
- Microsoft Dynamics 365 (Dataverse)
Read, copied with change tracking, version-checked writes, two-way sync.
- Microsoft Dynamics 365 Business Central
Read, copied, version-checked writes, two-way sync.
- Oracle NetSuite
Records read with SuiteQL, copied and written back.
- Odoo
Read, copied, written back, invoices posted, confined by company.
- Any OData v4 service
Read, copied, version-checked writes and actions.
AI models and coding agents
Chosen per application, agent or task behind one contract, with every model call attributed to the organization and the case it served.
- Anthropic
Language models and a coding agent.
- OpenAI
Language models, embeddings, images and a coding agent.
- Google Gemini
Language models.
- Mistral AI
Language models and scanned-document reading.
- xAI Grok
Language models.
- Perplexity
Language models.
- OpenCode
A coding agent over the Agent Client Protocol.
Sign-in and identity
Staff and customers sign in through the identity they already have, and accounts follow the company directory.
- Microsoft, Google, Apple and GitHub
Sign-in with an account people already have.
- Any OpenID Connect identity provider
Enterprise single sign-on per organization.
- Any SAML 2.0 identity provider
Enterprise single sign-on per organization.
- SCIM 2.0 directories
Accounts provisioned and removed from the directory.
Email and messages
One email contract, so the vendor is a configuration choice; text messages for notices and one-time codes.
- Resend
Transactional email, and email received into the application.
- Twilio SendGrid
Transactional email.
- Brevo
Transactional email.
- Postmark
Transactional email.
- Mailgun
Transactional email.
- Mailchimp Transactional
Transactional email.
- TwilioPartial
Text messages and one-time codes.
Payments
Plans, subscriptions and invoices kept in step with the payment provider.
- Stripe
Subscriptions, invoices and payments.
Files and documents
Files can stay in a person’s own drive, and scanned documents become text the application and its agents can use.
- Google DrivePartial
Files kept in a person’s own drive, or linked from it.
- Microsoft OneDrivePartial
Files kept in a person’s own drive.
- DropboxPartial
Choosing a file from a person’s Dropbox.
- Azure AI Document Intelligence
Scanned documents read into text, from the module registry.
Work tools
Vendor modules installed from Wildo’s module registry become the application’s own code, used through each person’s connected account.
- Asana
Tasks created in a person’s workspaces and projects.
- Microsoft Teams
Teams, channels, chats and messages.
Monitoring, analytics and evidence
What the application and its agents did, observed and kept where it can be checked.
- PostHog
Model-call traces and product analytics.
- SentryPartial
Errors in the browser.
- Better Stack
Telemetry.
- immudb
An independent, tamper-evident audit ledger.
- Google reCAPTCHA
Form submissions verified.
- Google Places
Address lookup.
Open standards
What a vendor that is not listed can still be reached with.
- OData v4 and v2
Business data services.
- Model Context Protocol and Agent2Agent
Business operations and agents opened to outside agents.
- CEF, LEEF and OCSF
Security events exported to a SIEM.
More than 200 connectors at launch
Beyond the services listed above, Wildo’s module registry opens with more than 200 connectors to the business services companies use every day. Each installs with one command and becomes the application’s own code, used through the account of the person or organization that connects it.
- CRM and sales
- Marketing and email campaigns
- Customer support
- Project and work management
- Team messaging
- Documents, forms and e-signature
- Accounting, payments and finance
- HR and recruiting
- Scheduling
- File storage
- Data and analytics
- Developer and operations tools
- E-commerce
A vendor that is not listed
An integration is a declared module, not a fork of the framework, so the next vendor is added the same way the listed ones were.
- Your own module
An application authors a provider for a vendor of its own.
- A registry module
Installed with one command and owned by the application.
- Another ERP
Any OData v4 service, or one new vendor description.
SAP and SAP S/4HANA are trademarks or registered trademarks of SAP SE in Germany and other countries. Salesforce is a trademark of Salesforce, Inc. Microsoft, Dynamics 365, Dataverse, OneDrive, Teams and Azure are trademarks of the Microsoft group of companies. Oracle and NetSuite are registered trademarks of Oracle and/or its affiliates. Odoo is a trademark of Odoo S.A. All other product and company names are trademarks or registered trademarks of their respective owners. They are used here only to identify the products Wildo works with, and their use implies no affiliation with, sponsorship by or endorsement from those owners.
Building a B2B product or an internal tool?
Wildo is not self-service yet. Tell us what you have in mind and we will say plainly whether it fits, and what happens next.