Pachca: the cloud
alternative to
self-hosted chat.

One of the main reasons companies go with open-source chat apps is the low cost. The software itself is free, so you only pay for the servers it runs on. But once you're up and running on a self-hosted app, the hidden costs start piling up: a team to install and maintain it, custom features for your needs and so on. For a 1,000-person company, maintaining a self-hosted app costs about as much as the salaries of 10 developers and DevOps engineers. Even on its most expensive plan, Pachca comes out 3 times cheaper.

As your user count grows, so does the load on the system, and the cost of maintaining it grows right along with it.

With Pachca, you just pay for a subscription for the number of users you need. Supporting the app, running the servers and building the product are all on us.

When you run a chat app on your own servers, every update from its developers can cause extra headaches. An update with new features might break message sending, notifications or some other part of the app.

That's why many companies skip upstream updates and build the features or plugins they need themselves, so they don't have to keep up with the latest version. But that means building an entire product in-house. You either have to staff a separate team for it or pull serious resources from your core one.

In Pachca, updates ship almost every week, and you never have to worry about them breaking anything.

That means most of the automations you'd want to build on a self-hosted app can be done in Pachca. With the API, you can:

- Handle all administration
- Take actions on behalf of users
- Pull aggregated data exports for analytics
- Get webhooks for all kinds of events
- Do everything a regular bot can

In other words, you can build just about anything on top of Pachca. Education companies have already built a successful student support system on it, for example, and Lamoda runs its entire office in Pachca.

When you maintain a service yourself, every outage and broken feature is on you. So if someone can't send messages or attach files, you're the one explaining to the whole company why it happened and when it'll be fixed.

When you work with Pachca under a contract, we guarantee a 99.9% uptime SLA, and that level of uptime applies to all of our users. You can check it for yourself on our status page.

If you deploy a chat app on your own servers and customize it yourself, regular employees have pretty much no one to ask simple questions. Say a feature doesn't work the way they expect: there's no help center or support team to help them sort it out.

Pachca support answers every request within 15–20 minutes, and it's free. We also have a large Help Center with more than 100 articles on how everything works.

Pachca has a powerful admin tool: tags. Use them to group people by any attribute ("marketing_team", "Moscow_office" and so on), then use those groups to add people to chats. To invite employees to a new chat, just add the right tags to it, and everyone with those tags shows up automatically. It works the other way too: when a new hire joins, assign them the right tags and they're instantly added to every chat they need.

Every Pachca user can share feedback on how the app works, and we always listen. What's more, we plan and prioritize product development based on what users ask for. That flexibility is possible because Pachca is the core product of an independent company, so we can build it in whatever way works best for the people who use it.

See what we've already shipped based on user requests in our public roadmap.