Update introduction #400

cspell.json

@@ -4,7 +4,14 @@
   // language - current active spelling language
   "language": "en",
   // words - list of words to be always considered correct
-  "words": ["Kubernetes", "Linkerd", "Quickstart", "quickstarts", "Zuplo"],
+  "words": [
+    "Kubernetes",
+    "Linkerd",
+    "proxying",
+    "Quickstart",
+    "quickstarts",
+    "Zuplo"
+  ],
   // flagWords - list of words to be always considered incorrect
   // This is useful for offensive words and common spelling errors.
   // For example "hte" should be "the"

docs/articles/what-is-zuplo.md

@@ -3,14 +3,15 @@ title: What is Zuplo?
 ---
 
 Zuplo is a light-weight, fully-managed API Management platform, built for
-developers (GitOps, fast deployment, unlimited preview environments etc.). We're
-working with engineering leaders to quickly add:
+developers (GitOps, fast deployment, unlimited preview environments, etc.).
+Hobbyist developers and Engineering leaders alike use Zuplo to quickly:
 
-- rate limiting
-- auth and access management,
-- programmable layer of abstraction between an API and its consumers (you can
-  write code that executes inside the Gateway)
-- full policy library
+- [Add auth and access management](./step-2-add-api-key-auth.md)
+- [Add rate limiting](./step-3-add-rate-limiting.md)
+- Implement a programmable layer of abstraction between an API and its consumers
+  (you can write code that executes inside the Gateway)
+- Generate a [rich developer documentation experience](./developer-portal.md)
+  with self-serve auth management and monetization
 
 Zuplo doesn't come with the crazy costs, training courses, etc. of a traditional
 API Management platforms, like Apigee or Azure APIM.
@@ -19,7 +20,99 @@ Zuplo embraces shift-left and infrastructure as code - the gateway definition is
 all stored in text files that can be source controlled. We can deploy a new
 environment, to the edge, in under 20s with a simple git commit.
 
-We're doing over 1.5 billion API requests per month, supporting API-first
+We're doing over 4.5 billion API requests per month, supporting API-first
 engineering teams of 5-50. Zuplo was created by the founder of Azure API
 Management and is backed by the founders of some of the most exciting
 developer-centric solutions like Auth0, Snyk, and BigID.
+
+Sound interesting to you? You can
+[see Zuplo in action](https://book.zuplo.com/meeting?utm_source=blog) or
+[get started with Zuplo](https://portal.zuplo.com/signup?utm_source=blog) for
+free.
+
+## Zuplo in your stack
+
+Zuplo's core offering is a fully-managed, serverless gateway that runs at the
+edge, in over 200 data-centers around the world. This has a number of advantages
+as a gateway including:
+
+- extreme redundancy and high availability built-in
+- within 50ms of everybody on earth (amazing cache performance)
+
+For this reason we consider the platform to be multi-cloud and have customers
+with backends in AWS, Azure, GCP and private data-centers. We have multiple
+options for securing connectivity between Zuplo and your backend API documented
+[here](./securing-your-backend).
+
+Zuplo typically sits between your clients and your backend (or origin) API. Your
+clients could be other servers, mobile devices, browsers running websites or IoT
+devices. The traffic is proxied through the Zuplo gateway where you can enforce
+protections like rate-limiting and authentication, validate requests before they
+hit your backend and much more.
+
+![Zuplo Architecture](https://cdn.zuplo.com/assets/9a9a490a-9bda-46f6-bcc8-c2e67809c0af.png)
+
+We also have customers that have globally distributed backends (hosted by
+multiple clouds). In this case, customers have deployed Zuplo and route to the
+nearest data-center.
+
+![Global distribution with Zuplo](https://cdn.zuplo.com/assets/9ef54160-c412-4126-a275-4c2ccd3935ff.png)
+
+## Protocols
+
+Zuplo can proxy any HTTP traffic and works well with REST, GraphQL, WebSockets
+and other HTTP protocols (we have customers proxying SOAP over HTTP too). HTTP 2
+is supported.
+
+## Languages
+
+Zuplo is configured using JSON configuration files and can be easily extended
+using TypeScript / JavaScript. Your backend can be written in any language - we
+have customers with backends coded in Go, C, Node, .Net, etc. As long as it
+communicates via HTTP, Zuplo is a great choice.
+
+## Integrations
+
+We have support for integrations with Datadog (for monitoring, logging), GCP
+Cloud Logging and are adding new integrations on demand for customers quickly.
+Contact us if you need an integration that you don't see.
+
+## Runtime
+
+The Zuplo runtime is built on Web Worker technology - this is a server runtime
+based on web standards that supports JavaScript and WASM code, and is used by
+other services like Deno Deploy, Fastly, CloudFlare Workers and Vercel Edge
+Functions.
+
+This has several advantages including close to 0ms startup time for new nodes
+increasing both API performance, throughput and scalability.
+
+This makes Zuplo's extensibility easy to use as the concepts are the same as
+browser scripting and well documented on platforms like MDN (e.g.
+[Response Web API](https://developer.mozilla.org/en-US/docs/Web/API/Response))
+and are discussed in depth on platform like
+[stackoverflow](https://stackoverflow.com/).
+
+## Isolation
+
+All Zuplo runtimes and customer code execution is safely isolated (each project,
+even within the same customer account is fully isolated). Edge deployments run
+on web worker technology (on the cloudflare network by default) which provides
+high isolation guarantees.
+
+## Performance and latency
+
+Zuplo handles billions of request every month for our customers and has been
+load tested to comfortably exceed 10,000 requests per second (including API key
+security, rate-limiting and other policies).
+
+Zuplo adds minimal latency to your backend - typically milliseconds, depending
+on the complexity of your gateway. Our policies are highly tuned to reduce
+latency and are adjustable to optimize for different scenarios.
+
+## Multi-cloud
+
+Many zuplo customers connect with services in Azure, AWS, GCP and even running
+on raw metal in colo locations. Our unique edge deployment profile means we work
+great with your API wherever it is and have a selection of options for
+[securely connecting to your backend](./securing-your-backend.md).

docs/articles/who-uses-and-why.md

@@ -49,17 +49,17 @@ Stripe-quality experience in record time. Examples include:
 ## Launching a new API
 
 Most of our startup customers are looking to launch an API and want to achieve a
-'Stripe-quality' API experience for their customers quickly.
+'Stripe-quality' API experience for their customers quickly. This mean a highly
+performant and secure API with beautiful and up-to-date documentation and usage
+analytics.
 
-They also want to save time, money and engineering effort and avoid building out
-common features like API key authentication, rate-limiting, quotas, request
-validation and developer documentation.
+Zuplo makes this achievable for small teams, saving you time, money and
+engineering effort. Using Zuplo allows you to avoid building out common features
+like API key authentication, rate-limiting, quotas, request validation,
+monetization, and developer documentation.
 
-API Key authentication is non-trivial to implement and requires writing security
-critical code to safely store keys and help customer's self-serve.
-
-Our promise is that Zuplo should be cheaper and faster - than building these
-features yourself, while future-proofing your architecture.
+Our promise is that Zuplo should be **cheaper** and **faster** than building
+these features yourself, while future-proofing your architecture.
 
 ## Managing multiple APIs
 

sidebar.json

@@ -6,11 +6,7 @@
       "type": "doc",
       "id": "intro"
     },
-    "items": [
-      "articles/what-is-zuplo",
-      "articles/who-uses-and-why",
-      "articles/zuplo-in-your-stack"
-    ],
+    "items": ["articles/what-is-zuplo", "articles/who-uses-and-why"],
     "isExpandedByDefault": true
   },
   {
@@ -47,7 +43,6 @@
       "articles/securing-your-backend",
       "articles/custom-domains",
       "articles/testing",
-      "articles/zuplo-in-your-stack",
       "articles/log-plugins",
       "articles/metrics-plugins",
       "articles/opentelemetry",

src/app/page.tsx

@@ -30,9 +30,6 @@ export default async function Page() {
             <Link href="/articles/who-uses-and-why">
               Who uses Zuplo, and why?
             </Link>
-            <Link href="/articles/zuplo-in-your-stack">
-              Zuplo in your stack
-            </Link>
           </CustomTOCListContent>
         </CustomTOCListSection>
         <CustomTOCListSection>