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

Nylas.com | Full time | San Francisco | Onsite ~ but we'll help you relocate Do you like writing open source code as your craft? Want to work on something that impacts every single person on the internet but isn't creepy? Nylas.com is hiring Engineers and SRE's to build beautiful products using EMAIL as its base. If you like ownership, steady customers, and a challenge of building then please reach out to me personally or apply below. You'll work on * https://github.com/nylas/sync-engine * https://github.com/nylas/N1 * Improving developer happiness - https://nylas.com/blog/technical-debt/ ... * And whatever else it takes to move the massive amounts of data that we see Tech Stack: Python, Flask, Electron, React, MySQL, AWS https://nylas.com/jobs/

Glad to see you here. The first time I learned about Nylas (here on HN, can't find the link atm) someone complained rather loudly that the open-source version of the sync server doesn't support 'proper' authentication. I never saw a reply to that. Do you understand that criticism? Do you understand what they might've been talking about? Looking at GitHub I guess they were talking about https://github.com/nylas/sync-engine#nylas-api-service and the need to pass the id via basic auth/as username.

Probably the biggest thing is that it translates a traditional document-based data structure (mailboxes via IMAP) into a stateless, streaming transactional data structure. This allows N1 to be way more efficient and faster, and only load about 2% of the total data in your mailbox. The sync engine is essentially an abstraction layer for IMAP/SMTP/MIME/etc. This architecture has become pretty common in the past few years: Mailbox, Outlook Mobile (Acompli), Spark, Cloud Magic, Gmailify, and many more run similar systems. Although as far as I know, we're the only one who has open sourced our backend.:https://github.com/nylas/sync-engine We actually released the API layer before N1, and lots of developers use it for their own apps and pay us to run the infrastructure. If you're curious, the full docs here: nylas.com/docs/platform You can prett

It's not a ploy-- just a design choice. The cloud sync engine does a lot of heavy lifting so N1 is faster and efficient. It's also open source free software so you can run it yourself! https://github.com/nylas/sync-engine (I work at Nylas.)

N1 supports connecting to all the major email providers, as well as pretty much every obscure IMAP server run by your ISP! What's pointed out in the FAQ is just that it uses a cloud service component (also open source! http://github.com/nylas/sync-engine) that we developed first to make it easier to build clients.

Hey-- I work at Nylas. Would love any feedback you have for the site! There's a bit more info on our "Features" page: https://nylas.com/features/ In particular: > Nylas brings email into the 21st century with modern tools, RESTful developer APIs, and open source code. Integrating with Gmail or Exchange now takes minutes instead of months. Nylas is the easiest way to build an email app. Pretty much this means we talk IMAP/SMTP/ActiveSync/MIME so your app doesn't have to. Plus there are some nice new features, like a transactional "delta" endpoint and webhooks, which makes writing mail processing code a breeze. If you're a developer, the easiest place to dig in might be our docs: https://nylas.com/docs/platform or the open source sync engine: https://github.com/nylas/sync-engine We also shipped a new desktop email app this fall, which start

They have an open source email sync engine/REST API https://github.com/nylas/sync-engine and client https://github.com/nylas/N1

It seems that sync engine was AGPL licensed from the start https://github.com/nylas/sync-engine/blob/master/LICENSE