diff --git a/README.md b/README.md
index 40970b5..e011b96 100644
--- a/README.md
+++ b/README.md
@@ -1,9 +1,14 @@
 # Couchbase Rust SDK
 
+## Deprecation notice
+This branch/version of the SDK is deprecated and not in maintenance.
+We are now working on a fully native version of the SDK in the [nativex branch](https://github.com/couchbaselabs/couchbase-rs/tree/nativex).
+Once the native SDK is considered to be complete enough it will be moved into this (master) branch.
+
 [![LICENSE](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
 [![Crates.io Version](https://img.shields.io/crates/v/couchbase.svg)](https://crates.io/crates/couchbase)
 
-This is the repository for the official, community supported Couchbase Rust SDK. It is currently a work in progress and built on top of [libcouchbase](https://github.com/couchbase/libcouchbase/).
+This is the repository for the official, community supported Couchbase Rust SDK, built on top of [libcouchbase](https://github.com/couchbase/libcouchbase/).
 
 ## Requirements
 
@@ -50,4 +55,4 @@ pub fn main() {
 More examples can be found in the `examples` folder. Please open a ticket if something is not present or does not showcase what you need.
 
 ## Unsafe Code
-This code contains **unsafe {}** code blocks. Breathe slowly and calm down, it's going to be okay. The reason why we use unsafe code is so that we can call into `libcouchbase` which is a C library. The only unsafe code is found in the lcb part of the IO module. So if you experience a segfault, it will likely come from there. We are trying to even keep unsafe in there minimal, but by the nature of it, it is all over the place. We are also working on a pure Rust SDK with no unsafe code (hopefully), but until this ships and is mature we have to live with it.
\ No newline at end of file
+This code contains **unsafe {}** code blocks. Breathe slowly and calm down, it's going to be okay. The reason why we use unsafe code is so that we can call into `libcouchbase` which is a C library. The only unsafe code is found in the lcb part of the IO module. So if you experience a segfault, it will likely come from there. We are trying to even keep unsafe in there minimal, but by the nature of it, it is all over the place. We are also working on a pure Rust SDK with no unsafe code (hopefully), but until this ships and is mature we have to live with it.