Built to sit around your existing systems

AnswerBnB is architected so vendor systems are replaceable: every integration passes through a normalized adapter contract, never directly into the Knowledge, Context, or AI layers. Here's exactly what that means today, honestly labeled.

Available a real, live connector existsIn Development actively being builtArchitecture Compatible the adapter contract exists; no vendor connector yetPlanned future work, not yet started

Property Management Architecture Compatible

A real PMSAdapter interface and a reference (mock) implementation exist today and power the current Properties/Reservations/Guests model. No live vendor connector exists yet.

GuestyPlanned
HostawayPlanned
HostfullyPlanned
HospitablePlanned
LodgifyPlanned
OwnerRezPlanned
SmoobuPlanned
UplistingPlanned
iGMSPlanned
OctoratePlanned
HostifyPlanned
TokeetPlanned
Rentals UnitedPlanned
ChannexPlanned
TrackPlanned
AvantioPlanned
Beds24Planned
StreamlinePlanned
EscapiaPlanned

Ecommerce Architecture Compatible

A CommerceAdapter contract is defined so a real connector can be built cleanly; no vendor connector exists yet.

ShopifyPlanned
Shopify PlusPlanned
WooCommercePlanned
BigCommercePlanned
Adobe CommercePlanned
MagentoPlanned
Salesforce Commerce CloudPlanned
WixPlanned
Squarespace CommercePlanned
PrestaShopPlanned
OpenCartPlanned
EcwidPlanned
Shift4ShopPlanned
VolusionPlanned
Big CartelPlanned
Square OnlinePlanned
commercetoolsPlanned
SAP CommercePlanned
VTEXPlanned
ShopwarePlanned
MedusaPlanned
SaleorPlanned

CRM & Help Desk Architecture Compatible

CRMAdapter and HelpdeskAdapter contracts are defined; no vendor connector exists yet.

SalesforcePlanned
Salesforce Service CloudPlanned
HubSpotPlanned
ZendeskPlanned
IntercomPlanned
FreshdeskPlanned
FreshservicePlanned
Zoho CRMPlanned
Zoho DeskPlanned
ServiceNowPlanned
GorgiasPlanned
Help ScoutPlanned
FrontPlanned
KustomerPlanned
GladlyPlanned
DixaPlanned
PipedrivePlanned
Microsoft Dynamics 365Planned
SAPPlanned
Oracle CXPlanned
Jira Service ManagementPlanned

ISP & NOC Architecture Compatible

ISPAdapter and MonitoringAdapter contracts are defined; no vendor connector or network monitoring exists yet.

SplynxPlanned
SonarPlanned
PowercodePlanned
UISPPlanned
UbiquitiPlanned
MikroTikPlanned
RADIUSPlanned
SNMPPlanned
TR-069Planned

Communication Channels Architecture Compatible

Web chat and email are the channels the current architecture handles. A MessagingAdapter contract covers the rest; no channel connector below exists yet.

WhatsAppPlanned
SMSPlanned
MessengerPlanned
InstagramPlanned
VoicePlanned

Payments Architecture Compatible

A PaymentAdapter contract is defined, deliberately read-mostly — AnswerBnB's architecture does not initiate financial transactions through this interface without a separately-approved action.

StripePlanned
PayPalPlanned
AdyenPlanned
BraintreePlanned

APIs & Webhooks Architecture Compatible

A GenericAPIAdapter contract exists as a fallback for a vendor without a dedicated adapter, so ad-hoc vendor calls don't spread through the codebase.

REST APIsPlanned
WebhooksPlanned
Custom integrationsPlanned

These lists describe the ecosystems AnswerBnB's architecture is designed to connect with — not a claim that a live connector exists for every name shown. See FAQ for more on how to read these labels.