Skip to main content
For IT & tech teams

APIs. SSO. MCP server. No vendor lock-in.

Open architecture, role-based access, audit trails, and an MCP server when you're ready to plug AI tooling into your church data. Built so your tech team can sleep on Saturday night.

What IT teams ask before they sign

SSO and identity

Single sign-on for staff, role-based access for volunteers, and the ability to revoke access in one place.

Audit logs and compliance

Per-action audit trails across every module. Data residency that respects your country's expectations.

Custom integrations

Stable REST APIs, webhooks for events that matter, and an MCP server so AI agents can read and act on Floways data safely.

Data ownership and exit

Your data stays yours. We never sell it, never train external models on it, and we'll export it on request — no exit tax.

FAQ

Common questions

Do you support SAML / OIDC SSO?
Yes — talk to us about your IdP. SSO is included on Core, Complete, and large-church plans.
Where is our data hosted?
We host in the region closest to your country, with data residency commitments documented per region. The full security overview lives at /security.
Will you train AI on our data?
No. Your church's data is yours. We do not sell, share, or use it to train external AI models — that's one of our published commitments on the Why Floways page.

Plug Floways in. Lock nothing down.

Read the security overview, then book a technical session — we'll talk APIs, SSO, MCP and migration with your team.