sync-engine

We originally piloted using Nylas's APIs in our product about a year and a half ago. In that timespan, their pricing has changed significantly about 4 times and they do not seem like they have a particularly good grasp on their business model. They also, despite advertising 10 free test accounts, arbitrarily delete said accounts and then when you ask to get them reactivated you get connected with a sales rep. Their API sync-engine [0] either hasn't been updated since March, or hasn't been kept open source--neither of which is a great sign. We're currently using the open source Nylas sync engine in production as we were uncomfortable trusting an important feature of our product in a company that doesn't seem to have a firm idea of what they want to do. But with the seemingly abandoned open source project, we are now working on building out

Nylas | https://nylas.com/ | Mostly Backend (Systems+Ops) | San Francisco, CA (SoMa) | ONSITE Hi! We're Nylas. We’re building an email platform to let our customers build apps integrating with email, contacts, and calendar. Under the hood, our simple APIs are powered by a large open source Python codebase that syncs data from providers like Gmail, Yahoo, Microsoft Exchange, and others. Thousands of developers depend on this platform for critical parts of their applications, so performance, reliability, uptime, and consistency are a must. Most of our code is open source (https://github.com/nylas/sync-engine) and we heavily use open source software. We take pride in the diverse culture we’ve built (we just reached 50% women!) and are looking for more than raw technical talent == We're particularly looking for folks who == * Take personal pr

Their clients are. However, you would gonna need their sync-engine[0] on your own servers in order to avoid contacting Nylas servers. From what I understand, it's kind of a cloud API that makes some sense out of emailing protocols. [0] https://github.com/nylas/sync-engine

Nylas has somewhat of a weird model. The Nylas client doesn't connect to you mail provider directly, instead the Nylas client connects to the Nylas Sync Engine. It used to be that using this API for this was a couple hundred a year, per account. Both the client and the sync engine are open source, so you've always been able to host your own. https://github.com/nylas/sync-engine

It looks like you need to run your own sync engine. https://github.com/nylas/N1/blob/master/CONFIGURATION.md https://github.com/nylas/sync-engine Edit: Not sure what the latest update changes yet (much of the sync engine is local now?), but this thread looks like it has the latest info so far. https://github.com/nylas/N1/issues/3166

It's open source, at least most of it https://github.com/nylas/sync-engine