Microsoft national clouds
GCC High, DoD and 21Vianet accounts, each signed in and called in its own cloud; Nylas documents them as unsupported. N2
workwae connects Microsoft 365 GCC High, DoD and 21Vianet accounts next to Gmail, Microsoft 365 and IMAP, in one hosted API.
Nylas is ahead in places, listed in the table below; these are the gaps teams switch for.
GCC High, DoD and 21Vianet accounts, each signed in and called in its own cloud; Nylas documents them as unsupported. N2
Meetings are created, moved and canceled with the event; Nylas lists Webex as read-only. N7
IMAP accounts can add CalDAV and CardDAV settings to sync calendars and contacts; Nylas IMAP accounts have no calendar. N5
Nylas facts come from its own pages, checked October 17, 2026; superscripts link to the sources on the full comparison.
| workwae | Nylas | |
|---|---|---|
| Microsoft GCC High, DoD and 21Vianet | Yes Each in its own cloud. | No Documented as unsupported. N2 |
| Exchange on-premises (EWS) | No Servers allowing IMAP and SMTP connect as IMAP accounts. | Yes EWS connector. N3 |
| Calendar for IMAP accounts | Yes Through CalDAV. | No N5 |
| Zoom and Webex created with events | Yes Kept in step with the event. | Partly Zoom with your own Zoom app; Webex read-only. N7 |
| Webhooks | Yes Signed, logged and replayable, plus a change feed. | Yes Signed; also to Google Pub/Sub or Amazon SNS. N8 |
| Import refresh tokens you hold | Yes With accounts.create. | Yes Bring Your Own Authentication. N10 |
| Verified shared Google app | No Our app has not completed CASA; use your own, verified by you. | Yes CASA Tier 3, on annual Pro with Accelerator or as an Enterprise add-on. N11, N14 |
| Data hosting region | United States only, on AWS. | United States or Europe, per application. N13 |
| SOC 2 report | No Planned, not started. | Yes SOC 2 Type II, plus ISO 27001 and HIPAA. N14, N16 |
| Published pricing | No Agreed with each early-access team. | Yes From a free plan to Enterprise. N14 |
If your own Google or Microsoft app issued the grants, register it with the same client id and secret and import each token with accounts.create.
// Once per user, with the token your own app holds
const account = await workwae.accounts.create({
provider: "google",
refreshToken,
oauthAppId: googleApp.id, // your app, registered in the workspace
externalRef: user.id,
}); Not if your own Google or Microsoft app issued their grants and you hold the refresh tokens. Everyone else signs in once through hosted connect.
Not over EWS. Servers that allow IMAP and SMTP connect as IMAP accounts.
No, SOC 2 is planned and not started. Security describes how we protect connected accounts.
On AWS in the United States. There is no European region.
We are onboarding a small number of teams. Tell us what you are building.