Nylas Blog

Nylas | https://nylas.com | Senior Software Engineer | Remote in Canada (US based company) At Nylas, we specialize in making it easier for developers to add email, calendar, and contact management features into their applications. We provide tools called APIs, which streamline the integration of these functionalities, ensuring they are secure and effective. This enables better, safer, and more reliable communication within apps. I’m hiring a Senior Software Engineer for the Platform Team at Nylas in Canada. This is a great opportunity if you’re looking to work in a fast-paced startup environment, tackle challenging projects, and accelerate your professional growth. One thing I can promise you is that your day-to-day work will never be boring. Apply here: https://boards.greenhouse.io/nylas/jobs/4500583005

> Javascript based desktop IMAP client Nylas N1 is an example of this (and excellent, might I add)! https://nylas.com/

This is an awesome article, and has some similar ideas to what we are working on at Nylas. https://nylas.com/ I don't mean to steal this thread, but if anyone is interested in building the future of email (including this) I'd love to talk with you. [email protected]

Nylas | SRE | San Francisco, CA (ONSITE) | https://nylas.com | Full Time only Nylas is like a race car moving at 200 MPH, and you are a member of the pit crew--swapping the tires and refueling without slowing down! We're looking for a Site Reliability Engineer to take our infrastructure to the next level, with a focus on tools, availability, performance, and scale. Critical to this role is supporting the entire engineering org in moving quickly, which includes running our internal tooling infrastructure, creating systems that make migrations/alerts/tests easy to write and run, and further improving our continuous integration and deployment workflows. You should love measuring things, making data-driven decisions, and have excellent written communication skills. As this is an engineering role, you should also be comfortable writing substantial amounts of production-grade code (although it may not be your focus). Bonus points for a deep love for large distributed systems, a knack for creating elegant tools, and experience participating in an on-call rotation and running on AWS. Double bonus points for clear, direct communication and a call-it-like-it-is attitude. Some technologies we use: Python, AWS, MySQL, Redis, Ansible, Elasticsearch, Kafka, ZooKeeper If you're interested, please get in touch with spang at nylas dot com directly, or apply via https://jobs.lever.co/nylas/f6d54373-2702-4d34-b3f7-d9200308cb38. We welcome applicants of all backgrounds.

Nylas | https://nylas.com/ | San Francisco, CA (Mission) | Full-time, INTERNS, ONSITE | Frontend (JS), Backend (Systems+Ops) _ _ _ | \ | | | | | \| |_ _| | __ _ ___ | . ` | | | | |/ _` / __| | |\ | |_| | | (_| \__ \ \_| \_/\__, |_|\__,_|___/ __/ | |___/ Hi! We're Nylas and we're looking for help building the next generation email platform. We're building a missing piece of Internet infrastructure and are looking for frontend application engineers, designers, backend systems engineers and infrastructure/operations engineers to join us. Companies are building their core businesses around our email API right now. We have to be reliable, up all the time, and fast. We have more data for a single user than in most startups' entire database. We're scaling heavily and if you have experience with automated deployments, debugging running systems, release engineering, and on-call schedules, but are still comfortable writing code, this job might be for you. :) Many people spend their entire days buried in mail clients which haven't significantly changed in years. Yet have you ever met anyone who really loves their email experience? We want to change that. We're building a frontend framework to power the next generation of mail apps. Sound exciting to you? == We're particularly looking for folks who == * Take personal pride in their work and value autonomy and ownership * Want the chance to step up and lead a…

Nylas | https://nylas.com/ | San Francisco, CA (Mission) | Frontend (JS), Backend (Systems+Ops) _ _ _ | \ | | | | | \| |_ _| | __ _ ___ | . ` | | | | |/ _` / __| | |\ | |_| | | (_| \__ \ \_| \_/\__, |_|\__,_|___/ __/ | |___/ Hi! We're Nylas and we're looking for help building the next generation email platform. We're building a missing piece of Internet infrastructure and are looking for frontend application engineers and designers and backend systems and infrastructure/operations engineers to join us. Companies are building their core businesses around our email API right now, and that means we have to be reliable, up all the time, and fast. We have more data for a single user than in most startups' entire database. We're scaling heavily and if you have experience with automated deployments, debugging running systems, release engineering, and on-call schedules, but are still comfortable writing code, this job might be for you. :) Many people spend their entire days buried in mail clients which haven't significantly changed in years. Yet have you ever met anyone who really loves their email experience? We want to change that. We're building a frontend framework to power the next generation of mail apps. Sound exciting to you? Apply here. == We're particularly looking for folks who == * Take personal pride in their work and value craftsmanship, autonomy and ownership. * Want the chance to step up…

For those needing to deal with customers/clients/internal teams with Google Workspace/Outlook and wanting JMAP-style (though not JMAP) modern JSON APIs, Nylas might be a viable option: https://www.nylas.com/ Nylas pricing has gotten better recently, but is still quite high though - at $1.50/connected account/month at scale, it's likely material to your per-user margin if it's part of your SaaS offering. But if you have a use case where this is a no-brainer (like capturing/analyzing/building custom real-time UI around your internal sales team's emails) then it's remarkably powerful.

Paywall... google search on "productivity infrastructure" brings me to Nylas - https://www.nylas.com/ They seem to offer tools to use AI to help automate boring work tasks, possibly disrupting the lowest levels of white collar work.

I love calendar tools and my friends can attest to that. I think I've built at least one calendar app every year for the past however long. I love the idea of a calendar API (another example is Nylas - https://www.nylas.com/products/calendar-api/) b/c it means I could build for EVERYONE and not just a gsuite specific app (which is what I tend to do for simplicity of APIs). The problem I've seen with these is an inability to grow / monetize at the rate startups need to, and, while I love this, things I'm curious about are: 1. How big is this market? 2. Has anyone innovated on pricing here? 3. Are there really well-adopted calendar APIs you need to design for other than Exchange and GSuite?

Nylas | Senior Sales Engineer | SF | ONSITE, VISA | Full-time | https://nylas.com The Nylas Cloud APIs makes it an order of magnitude easier for companies to add email, calendar, and contacts integrations to their applications. By being at the core of business communication, scheduling, and contacts, we believe we can shape the future of how people work. Because our product is highly technical — it has to bridge the gap between several very old/proprietary protocols (IMAP, ActiveSync, Exchange Web Services) — we're looking for a seasoned sales engineer that will help our prospects and customers integrate with our APIs, all the way from the initial stages of the implementation up to signing a contract. I'm the hiring manager for this job, please apply by sending me an email directly at karim AT nylas.com

Nylas | San Francisco, CA + NYC | Full-time + Remote | https://nylas.com | Developer Success Engineer $80-110k Hey folks! I'm hiring another developer success engineer to join our team of 3 here at Nylas. We're a fast growing company with 34 awesome people. DSE: https://jobs.lever.co/nylas/96a06eac-35df-40c8-9f33-635f72510f26 We take our culture seriously: https://www.keyvalues.com/nylas See our handbook: https://github.com/nylas/handbook Email me: [email protected] and apply at the link above

Nylas | San Francisco, CA / New York, NY | Full-Time, Onsite | https://www.nylas.com The Nylas Cloud APIs power email, calendar, and contacts features in SaaS products ranging from CRM and marketing automation to recruiting tools, scheduling assistants, legal and real estate platforms, and more. The Nylas email API integrates with 100% of email service providers, allowing bi-directional email sync between your SaaS platform and your email client. To learn more about who we are, our engineering culture, and whether this is the right place for you, read our Key Values profile: https://www.keyvalues.com/nylas Here are our open roles: - Senior Software Engineer: https://jobs.lever.co/nylas/01b84c71-37b4-43fe-b950-ce43d195b231 Tech Stack: Python Mysql Redis HAProxy Linux Javascript React Elastic Search AWS Jenkins MyPy Flux Flow nginx Feel free to message me directly

Congrats on your work on Nylas -- 2.0 is shaping up great and is already my primary email client on Linux. Question: Will the revenue from the Pro product really support development and maintenance of the free product? The free product is perfect for my needs, none of the Pro features are that useful for me (and its too expensive - email accounts from Google or Fastmail are $5/month, Nylas Pro is $12/month on top of that just for the client). The free product, as is today, is easily worth $20-30, IMO. Additional Comment: https://www.nylas.com/pricing needs to be updated. A lot of the Pro features are now available in the Free 2.0 version.

I'm holding off my downvote to see if i can get a straight answer out of you. Nylas Mail bills itself as the best email app. Them's strong words, but maybe you're worth the claim? Let's see! I see from screenshots that Nylas has folders and labels. Can i use either of these in the following fashion? - i can have a tree structure of them - an email can be in two separate folders/labels at the same time - folders/labels can be configured to learn which emails to automatically sort into themselves, based on the email contents, by dragging and dropping the email into or out of them Ball's in your court. E: Bonus round! In this screenshot there's only 6 emails in the list: https://www.nylas.com/static/img/nylas-mail/[email protected] Is there a way to get a list of emails where each line is actually only a line of text tall?

> Are there any good ones left these days? Not really. I wish the Mozilla Foundation would rejuvenate their email client once and for all. I found Nylas N1[0] works well, it's cross platform which is a big plus and has plenty of kb shortcuts. [0]: https://nylas.com/

> relies on a remote server. That isn't really a fair comparison when eschaton says > it has some weird server component that's not Github's own API server. The remote servers that Mail.app communicates that are... the email providers. As far as I'm aware, when I use Mail.app with Fastmail, Apple doesn't send all my Fastmail email through their servers. Mail.app talks directly to Fastmail. A mail client which works like Ship 2.0 would be Nylas[0][1]. For anyone who wants a bug tracker for GitHub Issues, JIIRA, or FogBugz which communicates directly with their issue tracking server[2] someone mentioned Bee[3] further down. [0]:https://nylas.com [1]:https://nylas.com/cloud [2]:http://www.neat.io/bee/security.html [3]:http://www.neat.io/bee/index.html

Not any more, per the post, the performance boost comes from using Gmail's, Exchange's, et al. APIs directly rather than remote IMAP sync + provide REST API for the client. Cloud now used for "much much much much less" [0] - just tracking and stuff. Sync-engine also (?) runs locally now, I'm not totally clear on how this works but there's apparently some currently closed source stuff to become open 'soon', so it should become clearer exactly what's going on. There's also apparently some details to follow on their engineering blog [1]. [0] - https://github.com/nylas/N1/issues/3166 [1] - https://nylas.com/blog

Good call - we updated the blog post with a link to https://nylas.com at the beginning. (Oh, Medium, you can be so fickle.) (I work at Nylas.)

> "Thunderbird" as a chrome application https://nylas.com/ https://github.com/nylas/n1

I made a "Show HN" post a while ago (https://news.ycombinator.com/item?id=6681238), found my current job thanks to it (https://nylas.com --- btw we're hiring) and moved to the US. Definitely life changing and I'm very grateful for it.

Isn't Nylas (https://www.nylas.com) supposed to fix this problem?

I went from Sparrow to Mailbox to Airmail. Sparrow was the best for its time. Mailbox had potential but was riddled with bugs. Airmail doesn't have the cleanest interface nor all the coolest features, but it's the best option I've found at the moment. For iOS I am still using Mailbox, but I guess now I have to use something else, will probably give the Gmail client a go. One OSX client I've just found that I'm hoping does what I need: https://nylas.com/N1 It's open source.

This is a bummer. Despite how incredibly buggy Mailbox is on OS X, it was still my favorite client since Sparrow. I might give Nylas[0] a try. [0] https://www.nylas.com/n1

I saw this on hacker news a while ago but it seems like a great alternative to thunderbird. I've used it and I really like the look and feel of it compared to thunderbird. I'm pretty sure I saw an option for IMAP too. It's called N1 and it's from Nylas. https://www.nylas.com/n1

How does this compare with Nylas (https://nylas.com), who claims they're the "next generation email platform"?

Nylas are, in addition to their open source sync engine: https://nylas.com/

Nylas | Product Manager, Product Marketing Manager, FP&A Analyst, BDR | REMOTE (US or Canada) | Full-Time | https://www.nylas.com Nylas provides APIs for email, calendar, and contacts, connecting to Gmail, Microsoft, IMAP, Zoom, Teams, and 250+ providers. Tens of thousands of developers use us to reach millions of their users. We're hiring across product, marketing, finance, and sales. Several of these roles benefit from someone who's a builder at heart. You don't need to be writing code, but you're using your favourite coding agent to experiment and solve problems day to day. High autonomy, close to customers, creative thinking rewarded. 100% remote in North America with regular in-person offsites. Product Manager | Remote US or Canada (pref: Toronto, Denver) | $120K to $160K USD / CA$120K to CA$160K. https://www.nylas.com/company/jobs/?ashby_jid=f4fdb62a-8a7e-45cd-b3b4-… Product Marketing Manager | Remote US or Canada (pref: Toronto, Denver, NYC, Bay Area). US: https://www.nylas.com/company/jobs/?ashby_jid=ebcf30ab-c9d1-4d77-a621-… Canada: https://www.nylas.com/company/jobs/?ashby_jid=2acb49b8-4e50-4829-830f-… FP&A Analyst | Hybrid Toronto (~3 days/week) | CA$75K to CA$100K. https://www.nylas.com/company/jobs/?ashby_jid=57ea11b2-8da0-49a0-a195-… BDR | Remote US (NY or Denver) | $65K to $100K USD OTE. https://www.nylas.com/company/jobs/?ashby_jid=bb13733d-da47-4143-b7a4-… BDR | Remote Toronto | CA$70K to CA$90K…

This exists: https://www.nylas.com

Hey! I'm an engineer on N1 and I can talk about (1) and (3): 1. Snoozing emails would be great. You could totally do this client-side in a plugin using our current developer APIs, by moving snoozed threads to a label/folder, and then moving them back after a prescribed time. Might be a fun project! Feel free to ping us on our community slack channel if you want to try. 3. N1 uses the exact same package structure as Atom, but we're using the CommandRegistry less, and introducing our own UI layer concepts like the ComponentRegistry (for dynamically injecting React elements.) There are probably a handful of Atom packages you could load into N1, but probably only well-contained ones with very minimal UI. Our composer unfortunately doesn't share any code with Atom's text view - we needed to do rich HTML editing, so we wrote our own composer based on `contenteditable`. Vim keybindings for the composer are also a great idea. There's actually an API for creating `DraftStoreExtensions` (https://nylas.com/N1/docs/DraftStoreExtensions.html), and if you implement `onInput` in your extension you can probably re-create vim keyboard handling. Unfortunately, that's a bit low-level: right now, the composer is not as easy to extend as Atom's editor. We've put a lot more effort into extensibility of the thread / message panels and views. Enjoy! Feel free to reach out on the community slack channel if you have any other questions.

Nylas | San Francisco, CA ONSITE (Open To Relocation) | Frontend (JS), Backend (Systems+Ops) Hi! We're Nylas and we're looking for help building the next generation email platform. We're building a missing piece of Internet infrastructure and are looking for frontend application engineers, designers, backend systems engineers and infrastructure/operations engineers to join us. Companies are building their core businesses around our email API right now. We have to be reliable, up all the time, and fast. We have more data for a single user than in most startups' entire database. We're scaling heavily and if you have experience with automated deployments, debugging running systems, release engineering, and on-call schedules, but are still comfortable writing code, this job might be for you. :) Many people spend their entire days buried in mail clients which haven't significantly changed in years. Yet have you ever met anyone who really loves their email experience? We want to change that. We're building a frontend framework to power the next generation of mail apps. Sound exciting to you? == We're particularly looking for folks who == * Take personal pride in their work and value autonomy and ownership * Want the chance to step up and lead a team * Put the work before ego. We've got each others' backs, and we want you to be with us on that == A bit more about us == * Our backend is built on Python, Flask, gevent, nginx, MySQL, AWS, and Debian. We've been careful to keep…