Integrations
DevSphere OS integrates with WordPress (with encrypted credentials), Stripe (payments and billing webhook), and an email provider. A hub lists connectors and connection tests; some data connectors are Planned or Coming Soon.
#Purpose
#Architecture
Integrations are configured from Settings and tested via connection-test endpoints. Secrets for integrations are encrypted at rest using a server-side passphrase.
WordPress connections store application passwords encrypted with pgcrypto (a dedicated encryption key). Stripe handles one-time checkout on the marketing site and sends a billing webhook the app verifies. Email uses the provider foundation (Resend today; SMTP stub).
#How it works
Configure
Encrypt secrets
Test
Use / receive
#Reference
#Integration status
| Integration | Status |
|---|---|
| WordPress | Available (encrypted credentials) |
| Stripe | Available (checkout + billing webhook) |
| Email (Resend) | Available |
| Email (SMTP) | Stub in this build |
| Analytics / Search Console / others | Planned / Coming Soon |
#Implementation notes
- WordPress application passwords are encrypted/decrypted with pgcrypto using a server-side key.
- Integration secrets (e.g., provider keys) are encrypted with a dedicated passphrase.
- Live WordPress publishing is additionally gated by a human publish-live approval.
#Limitations
Known limitations
- Some analytics/SEO data connectors are Planned or Coming Soon.
- SMTP transport is a stub; Resend is the supported email provider.
#Security considerations
Security
- Never store integration secrets in plaintext — they are encrypted at rest.
- Verify inbound webhook signatures (e.g., Stripe).
- Restrict integration management to admins.
#Best practices
- Test every connection after configuring it.
- Rotate integration secrets periodically.
- Confirm a connector is live before building on it.
#Related documentation
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.