Skip to content

About

Built by a company that wanted its chat back.

Smack started inside Wolfiz. We ran on hosted chat for years and kept hitting the same walls: per-seat bills that grew with every hire, client calls recorded into someone else’s cloud, big files sent through a third service, and admin controls locked behind the next tier.

So we built the chat we wanted to run ourselves. It lives on one server, signs people in with the IDs we already use, records to our own storage, and sends files from our own bucket. Then we used it every day and fixed what annoyed us, release after release.

“If it’s our company’s conversation, it should be on our company’s server.”

Smack is for companies like ours: big enough to care where their data lives, small enough to want one tool instead of four.

Principles.

  1. 01

    Your server is the product boundary.

    If a feature needs our cloud, it doesn’t ship.

  2. 02

    Every feature, every install.

    No tier decides whether you get IP policies or recording.

  3. 03

    Familiar beats clever.

    People should feel at home on day one.

  4. 04

    Say what it doesn’t do.

    Our security page lists the gaps.

  5. 05

    Ship small, ship often.

    Read the changelog.

Who makes it.

Smack is made by Wolfiz. Questions, partnerships or press: talk to us.

OUR CHAT. YOUR SERVER.

Docker Compose · Postgres · your S3 bucket · your domain