Fleep Logo

Fleep

Estonian team messenger that combines chat with email bridging, conversation tasks, pinboards, file sharing, and Business admin ownership of accounts and history.

EU-operated (EE)Email bridgingCloud SaaSAWS EU hosting (claimed)Business admin controls

Shortlist when you want an Estonian-operated messenger that mixes team chat with real email participation, light task/pin/file tools, and Business-side account ownership. Skip when you need E2EE, self-hosting, or a deep enterprise app marketplace — consider Nextcloud Talk (self-host) or Slack/Teams instead.

Key capabilities

Send to a conversation's unique email address, receive on username@fleep.io, create email threads with non-users, or connect an existing mailbox so external partners stay in the same work stream without mandatory Fleep accounts.

Create, assign, and track tasks inside the same conversation where decisions happen; Business adds a My tasks view across work. Suited to light coordination, not a full project-management suite.

Pin announcements so plans do not drown in scrollback; store and re-open shared files from a conversation-level drawer across web, desktop, and mobile.

Organization admins control Premium accounts and conversations—provision/deactivate users, reset passwords, manage membership and history access, set file retention, organization-wide teams, and company branding.

Public API for post/read of messages and files plus listed integrations (e.g. GitHub, GitLab, Jira, Zapier, Dropbox, Whereby for A/V). Not a self-hosted product.

Best fit when

  • SMEs that need chat plus partner/client threads over email without guest-only workspaces
  • Teams that want tasks, pins, and files inside conversations rather than a separate PM tool
  • Orgs that need admin ownership of accounts, leavers, and conversation history (Fleep for Business)
  • Groups piping notifications via API/webhooks into a simple messenger

Poor fit when

  • Requirements for client-side end-to-end encryption or zero-knowledge messaging
  • Mandatory self-host / on-prem or non-AWS residency
  • Heavy dependency on Microsoft 365, Slack app ecosystem, or large certified compliance packs (ISO/SOC not published)
  • Buyers who need a public live subprocessor register and recent third-party audit reports before trial

Consider instead when

  • When: You need self-hosted collaboration chat with full control of infrastructure

    Consider: Nextcloud (Talk) or other self-hosted groupware already in your stack

    Fleep is SaaS-only on AWS EU.

  • When: You need deep Microsoft 365 chat, meetings, and identity integration

    Consider: Microsoft Teams

    Fleep is independent of M365 but thinner on meetings/Graph.

  • When: You need the largest integration marketplace and channel-centric workflows

    Consider: Slack

    Fleep competes on email bridging and simplicity, not ecosystem breadth.

  • When: You want hosted European groupware with mail/calendar as the core

    Consider: Kolab Now

    Different product shape: groupware suite vs messenger-first.

  • Independent security / no-logs audit·Not found
  • ISO 27001·Not found
  • SOC 2 / SOC 3·Not found
  • GDPR / EU data protection·Vendor claimed
  • +3

Considerations & known limitations

  • MediumUS-group cloud and SaaS subprocessors

    Message storage on AWS (Dublin claimed) plus Google Analytics, Mixpanel, payment processors, and MailChimp (US marketing mail). Affects CLOUD Act / transfer diligence even with EE legal entity.

  • MediumNo public ISO/SOC or independent audit

    Assurance package for regulated buyers is thin on the public site; expect questionnaire and contractual annexes rather than downloadable certs.

  • MediumServer-side encryption, not E2EE

    TLS + encrypted storage on provider servers; unsuitable if policy requires client-held keys or provider-blind messaging.

  • LowPrivacy/Terms last dated 2019 on site

    Public privacy (Mar 2019) and terms (Jan 2019) may lag operational reality—confirm current policy versions and subprocessors during procurement.

  • LowNo self-host option

    Cannot place Fleep inside your own VPC or air-gapped network; residency limited to vendor AWS EU setup.

Open questions for due diligence

  • Will Fleep sign a B2B DPA and provide the current authorized-processor list in writing?
  • Is encryption-at-rest key management and employee access to message content documented for customer diligence?
  • Any ISO 27001, SOC 2, or independent penetration-test summary available under NDA?
  • Confirm whether Dublin remains the sole production region and whether backups leave the EEA.
  • Product roadmap and support SLAs for Business vs free trial users?

Häufig gestellte Fragen

No for email-mode collaboration. You can create email conversations or use conversation email addresses so non-users participate by ordinary email. Inviting someone into a normal Fleep conversation instead triggers a Fleep invite.

Public help materials describe TLS with forward secrecy in transit and encrypted storage of messages and files on Fleep's servers (Amazon EC2, Dublin claimed). That is server-side encryption under provider control, not a marketed zero-knowledge E2EE messenger. Confirm threat model and key handling with the vendor if required.

No public self-host or on-prem offering is documented. Fleep is a managed SaaS with servers on AWS in the EU (Dublin stated). Teams needing on-prem control should evaluate self-hosted options such as Nextcloud Talk or other open-source chat stacks.

Business gives the organization ownership of Premium accounts and conversations: delete/deactivate accounts, reset passwords, control conversation membership and history visibility, file retention policy, organization-wide teams, higher file storage, status messages, and company logo branding. Admins access Premium conversation content by joining the conversation.

About and security help pages place primary hosting on Amazon EC2 in Dublin, Ireland. The privacy policy also names Braintree/PayPal for payments, Google Analytics and Mixpanel for analytics, and MailChimp (US) for marketing mail. Request the current authorized-processor list and DPA before procurement.