diff --git a/README.md b/README.md
index a773ca766..b68ca4759 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@
- Cloud native log analytics
+ **Log Lake** for the cloud-native world
@@ -19,21 +19,19 @@
-Parseable is a log analytics platform, built for the modern, cloud native era. Parseable uses a index-free mechanism to organize and query data allowing low latency, and high throughput ingestion and query.
+Parseable is a **cloud native, log analytics platform, with a focus on performance & resource efficiency**. Parseable is useful for use cases where **complete data ownership, security and privacy are paramount**.
-To get started, download the Parseable binary from [releases page ↗︎](https://github.com/parseablehq/parseable/releases/latest) and run it on your machine.
+To experience Parseable UI, checkout [demo.parseable.com ↗︎](https://demo.parseable.com/login?q=eyJ1c2VybmFtZSI6ImFkbWluIiwicGFzc3dvcmQiOiJhZG1pbiJ9). You can also view the [demo video ↗︎](https://www.parseable.com/video.mp4).
-For comparison, Parseable consumes up to **_~80% lower memory_** and **_~50% lower CPU_** than Elastic for similar ingestion throughput. Read more in the [benchmarks directory ↗︎](./benchmarks/).
+## QuickStart :zap:
-For :stethoscope: commercial support and consultation, please reach out to us at [`sales@parseable.io` ↗︎](mailto:sales@parseable.io).
+
+Docker Image
+
-
+You can get started with Parseable Docker with a simple Docker run and then send data via cURL to understand how you can ingest data to Parseable. Below is the command to run Parseable in local storage mode with Docker.
-## :zap: Quickstart
-
-Deploy Parseable in local storage mode with Docker.
-
-```sh
+```bash
docker run -p 8000:8000 \
parseable/parseable:latest \
parseable local-store
@@ -43,7 +41,7 @@ Once this runs successfully, you'll see dashboard at [http://localhost:8000 ↗
To ingest data, run the below command. This will send logs to the `demo` stream. You can see the logs in the dashboard.
-```sh
+```bash
curl --location --request POST 'http://localhost:8000/api/v1/ingest' \
--header 'X-P-Stream: demo' \
--header 'Authorization: Basic YWRtaW46YWRtaW4=' \
@@ -57,55 +55,112 @@ curl --location --request POST 'http://localhost:8000/api/v1/ingest' \
]'
```
-## :rocket: Highlights
+
+
-- Choose storage backend - local drive or S3 (or compatible) object store.
-- Ingestion API compatible with HTTP + JSON output of log agents.
-- Query log data with PostgreSQL compatible SQL.
-- Single binary includes all components - ingestion, store and query. Built-in UI.
+
+Executable Binary
+
-### Enterprise ready
+You can download and run the Parseable binary on your laptop.
-- [Alerts ↗︎](https://www.parseable.io/docs/alerts)
-- [RBAC ↗︎](https://www.parseable.io/docs/rbac)
-- [OAuth2 ↗︎](https://www.parseable.io/docs/oidc)
-- [Grafana ↗︎](https://github.com/parseablehq/parseable-datasource)
-- [LLM ↗︎](https://www.parseable.io/docs/llm)
-- [Stats ↗︎](https://www.postman.com/parseable/workspace/parseable/request/22353706-b32abe55-f0c4-4ed2-9add-110d265888c3)
+- Linux
-## :dart: Motivation
+```bash
+wget https://github.com/parseablehq/parseable/releases/download/v0.9.0/Parseable_x86_64-unknown-linux-gnu -O parseable
+chmod +x parseable
+./parseable local-store
+```
-Traditionally, logging has been seen as a text search problem. Log volumes were not high, and data ingestion or storage were not really issues. This led us to today, where all the logging platforms are primarily text search engines.
+- MacOS (Apple Silicon)
-But with log data growing exponentially, today's log data challenges involve whole lot more – Data ingestion, storage, and observation, all at scale. We are building Parseable to address these challenges.
+```bash
+wget https://github.com/parseablehq/parseable/releases/download/v0.9.0/Parseable_aarch64-apple-darwin -O parseable
+chmod +x parseable
+./parseable local-store
+```
-## :trophy: Contributing
+- MacOS (Intel)
-[Contribution guide ↗︎](https://www.parseable.io/docs/contributing).
+```bash
+wget https://github.com/parseablehq/parseable/releases/download/v0.9.0/Parseable_x86_64-apple-darwin -O parseable
+chmod +x parseable
+./parseable local-store
+```
-
+- Windows
-### Contributors
+```bash
+Invoke-WebRequest -Uri "https://github.com/parseablehq/parseable/releases/download/v0.9.0/Parseable_x86_64-pc-windows-msvc.exe" -OutFile "C:\parseable.exe"
+C:\parseable.exe local-store
+```
-
+Once this runs successfully, you'll see dashboard at [http://localhost:8000 ↗︎](http://localhost:8000). You can login to the dashboard default credentials `admin`, `admin`.
-### License report
+To ingest data, run the below command. This will send logs to the `demo` stream. You can see the logs in the dashboard.
-A license report lists all the licenses of all dependencies in a project. You can use [cargo-about ↗︎](https://embarkstudios.github.io/cargo-about/) to generate a license report for the Parseable.
+```bash
+curl --location --request POST 'http://localhost:8000/api/v1/ingest' \
+--header 'X-P-Stream: demo' \
+--header 'Authorization: Basic YWRtaW46YWRtaW4=' \
+--header 'Content-Type: application/json' \
+--data-raw '[
+ {
+ "id": "434a5f5e-2f5f-11ed-a261-0242ac120002",
+ "datetime": "24/Jun/2022:14:12:15 +0000",
+ "host": "153.10.110.81"
+ }
+]'
+```
-If not already installed, install `cargo-about` using the below command.
+
+
-```sh
-cargo install --locked cargo-about && cargo about init
-```
+## Why Parseable :question:
-To generate a license report, run the below command.
+### Performance & resource efficiency
-```sh
-cargo about generate about.hbs > parseable-license.html
-```
+Parseable is written in Rust, with a clear focus on performance while ensuring a much lower CPU and memory footprint (compared to Java, Go based systems). When compared with Elastic, Parseable uses ~80% lesser memory and ~50% lesser CPU, while offering a better ingestion rate. This means you can run Parseable on smaller instances, saving costs.
+
+### Easy of use
+
+One of the key challenges users said they face today is the complexity of setting a logging system like Elastic. There are so many moving parts, and it's hard to get started. Parseable is designed to be simple to use, with a single binary that can be run on almost anywhere. The Console is built in the binary itself, so you can start using it without any additional setup.
+
+### Take control of your data
+
+With Apache Arrow and Apache Parquet as the underlying data formats, Parseable stores log data in an optimized, compressed manner as Parquet files. This means you get complete control and access to your data. You can use Parseable query and analysis, but also can plugin tools from wider Parquet ecosystem for further processing, analysis, and visualization.
+
+### Enterprise ready
+
+- High availability & Cluster mode
+- Local cache & storage
+- [OpenTelemetry support ↗︎](https://opentelemetry.io/)
+- [Alerts ↗︎](https://www.parseable.io/docs/alerts)
+- [Role based access control ↗︎](https://www.parseable.io/docs/rbac)
+- [OAuth2 support ↗︎](https://www.parseable.io/docs/oidc)
+- [Grafana based visualization ↗︎](https://github.com/parseablehq/parseable-datasource)
+- [LLM ↗︎](https://www.parseable.io/docs/llm)
+- [Stats ↗︎](https://www.postman.com/parseable/workspace/parseable/request/22353706-b32abe55-f0c4-4ed2-9add-110d265888c3)
-You can see the license report in the file parseable-license.html.
+## How do people use Parseable :bulb:
+
+- **Audit & Compliance** - Organizations that need to store logs in a secure, compliant manner. Parseable's direct to S3 bucket storage mode ensures that logs are stored in a secure, cost effective manner, and can be accessed only by authorized users, while all the data is queryable in real-time.
+
+- **Observability & Monitoring** - A very large chunk of observability data is logs. Organizations that need to monitor their systems, applications, and infrastructure in real-time use Parseable as the primary log storage system so they get timely alerts, and can analyze logs in real-time.
+
+- **Log Analytics** - Not all logs are created equal. For example application logs are seldom useful after a few days pass, but if same application also logs all the user interactions, that data is very valuable for product managers, and can be stored for a longer period. Several businesses store such high value logs and slice / dice them as needed.
+
+## Motivation :dart:
+
+Traditionally, logging has been seen as a text search problem. Log volumes were not high, and data ingestion or storage were not really issues. This led us to today, where all the logging platforms are primarily text search engines.
+
+But with log data growing exponentially, today's log data challenges involve whole lot more – Data ingestion, storage, and observation, all at scale. We are building Parseable to address these challenges.
+
+## Contributing :trophy:
+
+[Contribution guide ↗︎](https://www.parseable.io/docs/contributing).
+
+
### Supported by
diff --git a/USERS.md b/USERS.md
index c158012da..ec82da99b 100644
--- a/USERS.md
+++ b/USERS.md
@@ -2,7 +2,7 @@
The following document is a list of users and adopters who use Parseable. The users themselves directly maintain the list. You can add your organization by editing this file directly.
-If you're using Parseable in your organization, please add your company name to this list. It really helps the project gain momentum and credibility. It's a small contribution to the project with a big impact.
+If you're using Parseable in your organization, please add your company name to this list. It really helps the project gain momentum and credibility. It's a small contribution to the project with a big impact.
---