 Introducing Dark and Dimmed modes. Whether you're working late at night or deep undercover, these new themes are guaranteed to make you feel cooler.

As always, we have our community to thank for the inspiration. Dark mode has been requested more than any other feature.

To try dark mode, choose your theme in your account settings page (click avatar in top right corner, then settings).

If you have more feedback or feature suggestions, we're here to listen! Reach out to support@skiff.org anytime. Stay tuned for more on custom colors and themes.

So much of the difficulty with privacy and security

 products has little to do with the privacy or security itself. There’s nothing about verifying signatures or X25519 that warrants a clunky interface. And yet, we’re left with green text on black backgrounds, pop-ups that exist to dismiss, and tomes that describe arcane log in processes.

Security certainly adds new constraints. It can make good design harder. But too often, a carelessness towards design precludes the usefulness of the security in the first place. What’s the use of PGP, if your friend sends the wrong key by mistake anyway? (

Even PGP's creator got fed up with its design

Bringing user-friendly design to security matters. Technical skills cannot be a prerequisite to digital security. The people whose lives and reputations depend on it are rarely cryptographers or engineers themselves. And in a world of instant checkouts and auto-magic links even minor inconveniences can be a dealbreaker. We need to stop asking whether people care about privacy and start asking whether we, as designers and engineers, care enough about how people interact with privacy. If we’re truly to make the internet private for everyone –as we have set out to do at Skiff– usability must be front and center.

At Skiff, we’ve built a privacy-first platform for collaboration. Security is built into every feature and aspect of our product from onboarding to the emojis and the text editor. That means we've had to face usability challenges with almost everything we've built. We're still learning but along the way we've come up with a framework to help guide us. For each feature, we ask ourselves, does it:

anticipate, not dictate, a user’s actions?

make insecure behaviors difficult to perform?

require no extra effort compared to a less secure alternative?

reinforce an emotional sense of security?

People don't always follow instructions (no matter how pretty). They do what's convenient.

The principles behind these questions are hopefully straightforward: for 1 and 2, it's that users will do what's convenient regardless of any instructions; they set the constraints and decide the path, not us. For 3 and 4 – while users set the path, there's still a lot we can do to frame and organize it; it's our job to re-pave common actions and fence off undesirable ones (see image above). For 5, it's that any extra time cost should be put on us during development, not on our users; otherwise, it's impossible to be a true alternative. And 6 – for users to intuitively trust the product, the interface must reflect the underlying security.

Applying this framework to a real product is 

. Consider our account recovery process. When you forget your password on Skiff, there’s not much we can do since we don’t store passwords in any form on our servers (we use zero-knowledge proofs for authentication). Users instead need to generate a random symmetric key that they store physically. This can reduce account safety to a crumbled up piece of paper and lead to a bad experience for forgetful users.

Skiff’s design and security teams worked closely together to make this process smoother and more secure. Our security team integrated 

 to split the recovery key into three pieces. Now, one key is stored on paper, another in the browser, and a third is encrypted and stored on the server. To recover an account, two out of the three shares must be combined. This ensures that at no point can the server decrypt user data, while still giving forgetful users a backup on their browser.

Our design team, meanwhile, updated the onboarding UX to make it nearly impossible for a user to misconfigure their recovery keys. This all comes together in the most boring way possible (we hope). When you forget your password, you check your email inbox and set a new password. It just works. For all the extra implementation details, the user actually has to do 

Skiff’s public link feature follows a similar template. It implements a novel cryptographic protocol to ensure Skiff never has access to the link or document. But as far as users are concerned it’s just a toggle – same as any site.

Make no mistake – secure design isn’t always about invisibility. Being conspicuous serves a critical purpose too. Responsive indicators, well-placed labels, even sounds and animations can create a sense of security. As long as the design is honest, these components can reinforce and validate the actual security.

Other more subtle factors also play a role. When it comes to tone and voice, we’re careful to avoid exclamations, excessive emojis, and condescending descriptors like “my documents.” It's hard to trust a platform, if it's too playful.

We still have some pixels to push (like the ones in the envelope icon above).

Down to the last pixel, we also strive for every element to be aligned, centered, and perfectly set. It's not out of unbridled perfectionism. A single visual artifact puts in question all the things you can’t see. And in aggregate, it's unsettling even if subtle.

There’s a reason Skiff doesn’t default to dark mode. As tempting as monospace type and command-line interfaces can be, they alienate often more than they help. The initial coolness of feeling like a hacker might build some sense of security, but it's short-lived. Fun becomes gimmicky. And over time, these references can detach how the product looks from the how the product actually works.

We're currently putting these principles to work at Skiff, but there's still much to improve.
‍
If you’re working on your own security projects, feel free to fork and contribute to our open source design system: 

Finally, for product engineers and designers excited by the intersection of security and usability – if you want to help us craft new design patterns for a privacy-first future, 

Secure Design Patterns

If you use a diverse range of strong passwords, it’s a near certainty that you’ll forget some of them (that is, unless you’re using 

For some people, this happens so often that hitting “Forgot your password?” becomes just another part of logging in. 

 that the average American has been locked out of 10 accounts in the last month.

At Skiff, we’re building collaboration tools designed to eliminate the trade-off between privacy and usability that we all face when working and communicating online. So we don’t design for best-case scenarios or cyber-security experts. We use 

 that anticipate the needs of real, busy, messy people — people who forget their passwords 

Standard password-reset systems are fundamentally incompatible with an 

 platform that puts people in control of their own data. So we needed to design a new one: 

a password-reset system that simultaneously respects real people’s needs

 As with many things in secure software design, it wasn’t easy.

While the details vary somewhat from one platform to another, the broad outline of how account recovery usually works is pretty straightforward:

This may be via an emailed link, a security question, an authentication prompt on a device you’ve associated with your account, or some combination of these.

Step 2: You reset your password, and the platform swaps your old password for your new password (hopefully not in plain text).

Somewhere in a nondescript data center — buried in a server that’s leased or owned by your favorite (or least favorite) tech company — there’s a row in a data table with your username and password.

In theory, your password is not stored in plain text — rather, it’s been transformed into an illegible string of characters via a one-way cryptographic process called hashing. In reality, 

 (and many, many other platforms) have all been revealed to have stored passwords in plain text.

Either way, the login credentials in that table are updated so that the next time you log in, you’re able to use the new password.

Step 3: The platform restores access to your data.

You now use your new password to log in and the service provider restores access to whatever data were stored on your account, be they banking details or personal notes.

This process is simple. But its simplicity hinges on an important detail: 

 on the company’s servers, but in any case, the platform is able to — when it chooses — access your data and make decisions about when to grant you (or anyone else) access. When you change your password, the platform simply updates the conditions necessary for accessing the data that you’ve stored on its servers.

The simplicity of this process reveals how insubstantial the password was to begin with. Your password can be easily changed because it never controlled access to your data in the first place — the platform did.

But the three simple steps above don’t work for Skiff. We can’t cheat and arbitrarily change the conditions necessary to access your data, because…

No, really. We don’t have it. We store an encrypted version of your data on our servers, but we don’t have the keys to decrypt it and we never did. That comes with the territory of end-to-end encryption.

Only you, the end user, have the keys to your own data. So where are they?

If you want all the details, we recommend reading our 

. But the short version is that your password is the key to your data.

Every time you log in to Skiff, your browser uses your password to derive a key that’s used to decrypt the account data sent to your device by Skiff’s servers after a successful login. This all happens locally on your device. 

Your password and the key derived from it are never sent over any network nor stored in any form

The fact that your password remains private — even from us — is important, because it ensures that the system remains end-to-end encrypted. If we had access to your password, we would be able to use it to decrypt your data, and end-to-end encryption would be broken.

we don’t ever want to see or store your password

. We don’t even want to store it in a hashed or encrypted form (like most platforms do), because if it ever got into the hands of a motivated adversary, there are ways they could try to crack it.

So we have a problem: How does Skiff confirm you are who you say you are? How do we confirm the password you enter matches the password you set if we’ve never 

 your password in any way, shape or form?

The answer is the Secure Remote Password protocol (SRP), a clever piece of cryptography that allows a user to authenticate their identity to a server without ever sending the password (even in a hashed or encrypted form) to that server. (For more information on how SRP works, check out 

Using the Secure Remote Password protocol, we’ve solved one important problem — we’ve authenticated your identity without ever having seen or stored your password in any form. And in the process, we’ve ensured that a password on Skiff does what many people mistakenly (though understandably) assume it does on every platform: It genuinely limits access to your account. 

Without your password, no one — not even we — can access your data.

But we’ve also introduced a new problem: If you forget your password at this point, your data will be impossible to recover. Remember, Skiff doesn’t have access to your password nor your unencrypted data. So if you lose your password, then all we could do is give you back encrypted data, which would be as useless to you as it is to anyone else.

When you sign up as a new Skiff user and log into your account, the first thing we ask you to do is to enable account recovery. Doing so gives you a long, randomly generated string of characters. This is the recovery key, a single-use backup option for decrypting your data if you forget your password. You can either write it down or download it as a PDF.

From that point on, if you forget your password, you’ll need to do two things to verify your identity:

Prove you have access to your registered email address by entering a time-limited passcode sent to your inbox

 initiate the password reset process using the same browser you last used to sign into Skiff

To keep this process secure, we use a technique called 

, which splits the backup decryption key for your account data into three pieces, or “secret shares.” After your decryption key is split up locally, you keep two shares — the first lives in your browser’s local storage and the second is the string of characters you write down or download — and you send us the third. (All of this happens automatically when you enable account recovery.)

The backup decryption key for your data can only be produced by combining at least two of the three secret shares. So after verifying your identity during account recovery, Skiff sends you the single share it was storing. If you supply at least one of the two shares you were storing, then you’ve now met the two-share threshold, and you can decrypt your data locally a single time. You then reset your password and your data is re-encrypted using the new password, before we — or anyone else — can ever glimpse it.

The advantage of this system is that we never have enough information to decrypt your data — we only ever have one of the three shares — but we can still support you in recovering your account if you ever lose access to one of your shares.

Behind the scenes, this process is more complex than a standard password reset, but for Skiff users, it’s seamless. The upshot is that your data stays private and secure, and we can still help you out if you’re among the 

 who forget their new password the moment they reset it. (And if you are, remember, 

Death, taxes and forgotten passwords

 out a new design for Pages (FKA documents) on Skiff. As tens of thousands of individuals and teams have signed up to use Skiff, we’ve received thousands of feature ideas and support requests via our 

. Many of these requests center on the same theme: making it easier to find and organize your information on Skiff.

Now, pages are structured with three new features: Titles, icons, and descriptions.

New page titles synchronize with your dashboard and file tree, making it easier for you to organize, find, and share pages in your workspace.

Icons enable creative customization for every page in Skiff. Click the icon at the top of every page (or to the left of page titles in the sidebar) to customize the page icon. Choose the icon and color that best fit your work.

Optional page descriptions provide additional context and information. To edit a page description, select the page’s title, and an area for description text will open. From there, add any relevant information, context, or descriptors to the page.

Comments or questions? Join our Discord here → 

New page design

We believe that open sourcing is an essential part of building trust

 around secure products. As a first step to completely open sourcing Skiff, we're sharing two key components of the Skiff codebase: our typed-AEAD envelope and UI component libraries.

As we scaled out our platform, it became important to be able to inspect metadata without having to decrypt objects. This would both save compute and prevent decryption of badly-formatted data.

Our authenticated encryption with associated data (AEAD) envelopes library allows us to embed additional information in the output of encryption functions. While the nacl family of envelope functions (e.g. secretbox) only support encryption-related metadata (e.g. nonces), our library is more extensible. We currently use our AEAD library at Skiff to validate data versions and types.

Skiff UI is a react components library for the Skiff UI Design System. It's currently in-use almost everywhere on our app. Over time we plan to continue adding more security and privacy-focused components to the library. Our hope is that Skiff UI will be able to spread usability to security products more widely.

The two libraries can be accessed at the following links: 

. We're releasing them under the GNU AGPLv3 license.

We look forward to having more eyes on our codebase, and appreciate any feedback. If you have any questions or ideas, feel free to reach out to us at hello@skiff.org.

Skiff is Open Sourcing

 to complete the privacy-first workspace. Our mission is to empower freer, more creative, and more expressive communication and collaboration - and a shared calendar brings us even closer to that future.

Our calendars store a corpus of our lives - our appointments, our contacts, or family gatherings, and much more. They contain a record of where we go - flights, coffee meetings, and birthday parties - and what we’re working on.

Calendars also integrate deeply into the modern workspace. Teams use shared calendars for important meetings; every iOS and Android device relys on calendars for appointments and notifications; event invites are a critical reminder for upcoming meetings or deadlines.

Skiff Calendar is an end-to-end encrypted, private calendar that integrates deeply with Skiff Mail, Drive, and Pages. Skiff Calendar allows sending events and updates to external users, syncs across devices, and is built to be completely privacy-first. Read on for more information about how Skiff Calendar works, how to sign up, and what features are available.

Skiff Calendar is an end-to-end encrypted digital calendar for managing your schedule, planning events, and inviting both Skiff and external users. Skiff Calendar is built to be privacy-first, keeping your external attendees private and end-to-end encrypted, and easy to use, with convenient features you’d expect from any other digital calendar.

We bulit Skiff to be a privacy-first, end-to-end encrypted workspace for collaborating and communicating. With hundreds of people now using Skiff, Skiff Calendar brings us even closer to realizing this vision.

Digital calendars have become a crutch for managing our work, schedules, contacts, and personal life. It’s estimated that 70% of internet-using adults use a digital 

. Given the deep intersections between email and calendar - as well as privacy and calendar events - building Skiff Calendar has been a high priority.

Skiff Calendar is available on the web, with mobile apps for both iOS and Android coming soon. Skiff Calendar is compatible with all major browsers, including Firefox, Chrome, Brave, Safari, Edge, and more. As mobile apps become available, Skiff Calendar will deliver notifications for invites, reminders, and upcoming events.

Every Skiff user has a Skiff Calendar available at 

 It’s free to use for everyone! If you are on a Pro or Business plan, you’ll also have access to a calendar, which can be used for your full team workspace.

If you are signing up for a new Skiff account, navigate to 

, then create your new account. From there, you’ll be able to choose Calendar from the top left corner.

Once you’ve opened Skiff Calendar, you can create events, send invites, and import existing ICS files. We’ll have more import methods coming soon.

Skiff Calendar keeps your private event information completely end-to-end encrypted, including the title, location, details, and all external recipients.

Can I invite exernal (non-Skiff) attendees?

Yes. You can invite any external attendee on another email provider, and they will receive an invite email that will allow synchronization of the event between your and your guest’s calendars. Furthremore, Skiff 

will not know the email address of your guest.

In the beta version, recurring events are not yet possible. They’ll be available soon!

Shared calendars will also be available in the next month outside of the beta version.

How does Skiff Calendar integrate with Skiff Mail?

Events you receive in your Skiff Mail inbox will automatically appear in your Skiff Calendar. Likewise, any invite you send externally to other Skiff users or external users will integrate directly into their calendars, including RSVPs (yes, no, maybe) on events.

How can I download Skiff Calendar on iOS, Mac, or Android?

 links to Mac, iOS, and Android applications. Currently, Skiff Calendar is available on the macOS app and in the web; iOS and Android applications will be released shortly.

Skiff Calendar Launches!

The Skiff Drive iOS app is launched! Download it at 

. Skiff Drive is a platform for end-to-end encrypted file storage and sharing. You can upload, view, share, and download files of any type, from documents to Excel spreadsheets. In this blog, we’ll walk through some of the capabilities of the new Skiff Drive mobile app.

Our digital files store more personal information than our homes. From medical records and personal journals to job applications and client reports, drive storage holds our life’s work and history.

Skiff is an end-to-end encrypted, privacy-first workspace for your most sensitive work. Given this mission to empower the world to work more freely and effectively - to be people, and not products - drive storage for files and data is a core, critical part of this mission.

Earlier this year, we launched the first 

 of Skiff Drive to enable uploading and viewing files on the web. Today, we make Skiff Drive simpler, more powerful, and more intuitive with the launch of an end-to-end encrypted file storage app for iOS.

Cloud storage enables users to upload files, data, and other information into servers operated by cloud providers. These cloud storage providers are responsible for keeping the data available and accessible, and the physical environment protected and running. People and organizations buy or lease storage capacity from the providers to store user, organization, or application data.

Cloud storage services can be utilized from a public network, private network, or hybrid network of both public and private access. Cloud storage often provides data redundancy, storing identical copies of data in multiple physical locations to protect data in the event of equipment failure or natural disasters. Users can access data stored on remote servers by using a web browser or a mobile app.

As we store more and more sensitive or personal data in the cloud, it becomes critically important to make sure that our data is properly secured. End-to-end encrypted cloud storage is the highest standard in cloud storage security and ensures that your data is safe from prying eyes.

Everything on Skiff Drive is end-to-end encrypted and private to you

By encrypting your data before it is uploaded to the cloud with keys that are known only to you, Skiff Drive will ensure that only you and shared recipients can ever access your data. This is especially important for businesses who may store customer or client data in the cloud. By encrypting that data, businesses can help ensure that their customers' information is safe, increasing trust for all users.

Immediately on opening the Skiff Drive app, the interface allows for direct upload of files using the upload button in the bottom right corner. Simply tap this button to start uploading files to your Workspace.

After you’ve selected a file, you are taken to an in-app viewer, which can preview most types of commonly shared files. In the top right corner, the Share button allows you to share the file with other Skiff users, or to generate a shareable link that can be transmitted in any messaging app (or via 

On Skiff Drive, you can also download files to your device, including in the new iOS app. This enables sending, receiving, and downloading files for offline use or later viewing.

Every Skiff user is granted 10 GB in free storage for mail, files, notes, and more. For more storage, you can upgrade to the Pro plan for 100 GB of storage, and 1 TB of storage on the Business plan.

If you have feedback on this first release, please feel free to contact us at support@skiff.org, DM us on 

 and send a message to the group. We also wrote a longer blog on 

 and a lengthy technical overview on why end-to-end encryption 

Skiff Drive iOS app launched

The Node.js crypto library is a built-in module that provides cryptographic functionality for Node.js applications. It includes a range of features, such as support for generating cryptographic keys, encrypting and decrypting data, and creating and verifying digital signatures.

The Node.js crypto library uses the same cryptographicalgorithms and protocols as other secure systems, which ensures that the cryptographic operations it performs are just as secure. It also includes mechanisms for ensuring the integrity of cryptographic operations, such as support for digital signatures.

The Node.js crypto library is easy to use and can be integrated into Node.js applications with just a few lines of code. It is widely used in the Node.js community and has become an important part of the Node.js ecosystem.

Overall, the Node.js crypto library is a valuable tool for Node.js developers who need to perform cryptographic operations in their applications. It provides a range of features and is easy to use, making it a popular choice for implementing cryptography in Node.js applications.

To start, you will need to have Node.js installed on your system. You can download the latest version of Node.js from the official website (

Once you have Node.js installed, you can use the following steps to encrypt and decrypt a message using the Node.js crypto library:

1. Create a new Node.js project by running the following command:

2. Create a new JavaScript file, named app.js, and add the following code to import the Node.js crypto library:

3. Add the following code to generate a random encryption key:

4. Add the following code to define the message that you want to encrypt:

const message = 'This is the message that we want to encrypt.';

5. Add the following code to encrypt the message using the encryption key that you generated previously

const cipher = crypto.createCipheriv('aes-256-cbc', key, iv);

let encrypted = cipher.update(message, 'utf8', 'hex');

6. Add the following code to decrypt the encrypted message using the encryption key that you generated in step 4:

const decipher = crypto.createDecipheriv('aes-256-cbc', key, iv);

let decrypted = decipher.update(encrypted, 'hex', 'utf8');

7. Add the following code to print the encrypted and decrypted messages to the console:

console.log('Encrypted message:', encrypted);

console.log('Decrypted message:', decrypted);

8. Run the following command to execute the JavaScript file and encrypt and decrypt the message:

If everything works correctly, you should see the encrypted and decrypted messages printed to the console.

WebCrypto is a standard for implementing cryptographic operations in web browsers. It provides a set of APIs (application programming interfaces) that enable web applications to perform cryptographic functions, such as encrypting and decrypting data, securely.

One of the key reasons why WebCrypto makes browser cryptography secure is that it uses the same cryptographicalgorithms and protocols that are used in other secure systems. This ensures that the cryptographic operations performed by web applications are just as secure as those performed by other applications.

Additionally, WebCrypto uses a secure environment to perform cryptographic operations. This means that the cryptographic keys used by web applications are not accessible to other parts of the browser, or to other applications on the user's device. This helps protect against attacks that try to steal cryptographic keys or other sensitive information.

Furthermore, WebCrypto includes mechanisms for ensuring the integrity of cryptographic operations. For example, it includes support for digital signatures, which can be used to verify that a message or other data has not been tampered with. This helps protect against attacks that try to alter the results of cryptographic operations.

Overall, WebCrypto makes browser cryptography secure by using strong cryptographicalgorithms and protocols, providing a secure environment for performing cryptographic operations, and ensuring the integrity of cryptographic operations. These features help ensure that web applications can perform cryptographic functions securely and reliably.

To use WebCrypto, you will need to include the crypto object in your code. This object contains several methods that you can use to perform cryptographic operations, such as generating keys, encrypting and decrypting data, and signing and verifying data.

Here is a simple example of how to use WebCrypto to generate a random key and encrypt some data:

const key = crypto.subtle.generateKey( { name: "AES-GCM", length: 256, }, true, ["encrypt", "decrypt"] );

const data = new TextEncoder().encode("Hello, world!");

const iv = crypto.getRandomValues(new Uint8Array(12));

const encryptedData = crypto.subtle.encrypt( { name: "AES-GCM", iv: iv, }, key, data );

In this example, we first import the crypto object, which provides access to the WebCrypto API. We then use the generateKey method to generate a random AES-256 key that we can use to encrypt and decrypt data.

Next, we create a TextEncoder object, which we can use to convert a string into a Uint8Array of bytes. We then use the encode method to encode our string as a Uint8Array.

Finally, we use the encrypt method to encrypt our data using the key and an initialization vector (IV). The IV is a random value that is used to ensure that the encrypted data is unique for each encryption operation.

This is just a simple example of how to use WebCrypto. There are many other cryptographic operations that you can perform using this API, such as generating hashes, signing data, and building applications that rely on client-side crypto, such as Skiff’s suite of end-to-end encrypted 

Here at Skiff, we've open-sourced and MIT licensed our own, easy-to-use JavaScript encryption, decryption, and object versioning library. You can check out the library 

Skiff-crypto is designed to be functional, powerful, and easy-to-use. To encrypt and decrypt text, all you have to do is:

const skiffCrypto = require('@skiff-org/skiff-crypto');

const plaintext = "Hello, skiff-crypto!";
const keypair = skiffCrypto.generatePublicPrivateKeyPair();
const encrypted = skiffCrypto.stringEncryptAsymmetric(keypair.privateKey, { key: keypair.publicKey }, plaintext);

const decrypted = skiffCrypto.stringDecryptAsymmetric(keypair.privateKey, { key: keypair.publicKey }, encrypted);

console.log('Ciphertext:', encrypted);
console.log('Expected to be true:', plaintext === decrypted);

You'll find a suite of functions for encoding or decoding strings into byte arrays, object datagrams for managing versions and structure, and functions for generating and verifying signatures.

Hashing is the process of taking a piece of data and converting it into a fixed-size string of characters, known as a hash. Hashes are often used to store passwords because they are secure and difficult to reverse.

To create a hash in JavaScript, you can use the crypto library, which is built into modern browsers. Here is an example of how to create a hash using the crypto library:

const crypto = require('crypto'); // Create a hash

const hash = crypto.createHash('sha256'); // Update the hash with the data you want to hash

hash.update('my-data-to-hash'); // Get the final hash as a hexadecimal string

console.log(hashString); // Outputs a long string of characters

In this example, we use the sha256 algorithm to create the hash. This is a popular and secure algorithm, but there are many others to choose from. You can see a full list of supported algorithms by calling crypto.getHashes().

Encoding is the process of taking data and converting it into a different format. This is often used when storing or transmitting data, as different formats can be more efficient or secure.

In JavaScript, you can use the Buffer class to encode data into a variety of formats. Here is an example of how to encode data as a base64 string:

const buffer = Buffer.from('my-data-to-encode'); // Encode the data as a base64 string

const encodedString = buffer.toString('base64');

console.log(encodedString); // Outputs a base64-encoded string

In this example, we use the Buffer.from() method to create a Buffer object storing the relevant data. Then, we instruct the Buffer to convert the data to a string in base64. From there, the encoded output is printed to the console.

Other crypto libraries in Javascript, such as 

, simplify some of the interfaces and functions needed. For a tutorial on how to use this library, check out 

What products use cryptography in JavaScript?

Crypto libraries for the web and NodeJS have enabled a new generation of privacy-first web development. A few of our favorite examples are below:

 is an end-to-end encrypted, private workspace, with products for email, calendar, collaborating on notes, and file storage. The product performs key pair generation in the web using elliptic curves. Using asymmetric cryptography, Skiff Mail encrypts messages with recipients’ public keys such that only users’ individual private keys can decrypt messages and see the resulting plain text. Skiff Mail is free to use, with 10 GB of storage included, and offers paid plans for custom domains, extra storage, and business features.

Dark Mode

Related articles

Join the community