overview complete

Author: saminacodes

apps/portal/src/app/connect/pay/fees/page.mdx

@@ -24,7 +24,6 @@ You can configure who pays the protocol fee for buy or sell transactions by spec
 
 See full reference for [`buy`](https://portal.thirdweb.com/references/typescript/v5/buy/prepare) and [`sell`](https://portal.thirdweb.com/references/typescript/v5/sell/prepare). 
 
-
 #### Setting fees on transfers or purchase mode
 
 You can configure who pays the protocol fee for transfers or purchase mode using the `feePayer` setting. This affects the 

apps/portal/src/app/engine/features/backend-wallets/page.mdx

@@ -2,24 +2,24 @@ import { createMetadata, Details } from "@doc";
 import { Callout } from "@doc";
 
 export const metadata = createMetadata({
-	title: "Backend Wallets | thirdweb Engine",
+	title: "Server Wallets | thirdweb Engine",
 	description:
-		"Engine performs blockchain actions using backend wallets that you own and manage.",
+		"Engine performs blockchain actions using server wallets that you own and manage.",
 });
 
-# Backend Wallets
+# Server Wallets
 
 Engine performs blockchain actions using backend wallets that you own and manage.
 
 There are multiple options for securing backend wallets.
 
-## Smart Backend Wallets
+## Smart Server Wallets
 
-Smart backend wallets are the recommended way to perform blockchain operations with Engine. Each smart backend wallet consists of an EOA (managed internally by Engine) and a smart account (using thirdweb's default account implementation).
+Smart server wallets are the recommended way to perform blockchain operations with Engine. Each smart server wallet consists of an EOA (managed internally by Engine) and a smart account (using thirdweb's default account implementation).
 
 ### Benefits
 
-Smart backend wallets inherit smart account benefits and offer several advantages over traditional EOAs:
+Smart server wallets inherit smart account benefits and offer several advantages over traditional EOAs:
 
 - **Gas Management**: Built-in paymaster eliminates the need to maintain gas tokens. This means you never need to hold crypto or top up gas.
 - **Better Nonce Management**: Smart accounts use multi-dimensional nonces, which are more efficient than EOAs.
@@ -55,7 +55,7 @@ For AWS and Google Cloud KMS options, follow the setup instructions in the respe
 
 ### Pricing
 
-Smart backend wallets have no additional costs to use with your Engine instance. Transactions sent from smart backend wallets follow the [same billing model as regular account abstraction transactions with thirdweb](/connect/account-abstraction/infrastructure#pricing--billing).
+Smart server wallets have no additional costs to use with your Engine instance. Transactions sent from smart backend wallets follow the [same billing model as regular account abstraction transactions with thirdweb](/connect/account-abstraction/infrastructure#pricing--billing).
 Smart accounts need to be deployed on each chain. This costs gas and is billed to your account like any other transaction.
 
 ## Local wallet
@@ -80,7 +80,7 @@ An AWS KMS Wallet is a wallet securely stored in your AWS account. Engine can cr
    - `kms:Verify`
 1. On the user page, navigate to **Security credentials > Access keys**.
 1. Select **Create access key** to get an **Access Key** and **Secret Key**.
-1. In the dashboard, navigate to **Configuration > Backend Wallets**.
+1. In the dashboard, navigate to **Configuration > Server Wallets**.
 1. Select **AWS KMS** and provide the following:
    - Access Key (example: `AKIA...`)
    - Secret Key (example: `UW7A...`)
@@ -92,7 +92,7 @@ An AWS KMS Wallet is a wallet securely stored in your AWS account. Engine can cr
    - Key type: `Asymmetric`
    - Key spec: `ECC_SECG_P256K1`
    - Key usage: `Sign and verify`
-1. In the dashboard, navigate to **Overview > Backend Wallets**.
+1. In the dashboard, navigate to **Overview > Server Wallets**.
 1. Select **Import** and provide the following:
    - AWS KMS Key ID (example: `0489da75-9830-4a5a-97e3-e4a6df7775b3`)
    - AWS KMS ARN (example: `arn:aws:kms:us-west-1:632186309261:key/0489da75-9830-4a5a-97e3-e4a6df7775b3`)
@@ -109,7 +109,7 @@ An AWS KMS Wallet is a wallet securely stored in your AWS account. Engine can cr
 1. Navigate to the [Service Accounts](https://console.cloud.google.com/iam-admin/serviceaccounts) page. Select the above service account.
 1. Navigate to the **Keys** tab. Select **Add Key > Create new key**.
 1. Select **JSON** to download the JSON file. This file contains the key's private key in plaintext.
-1. In the dashboard, navigate to **Configuration > Backend Wallets**.
+1. In the dashboard, navigate to **Configuration > Server Wallets**.
 1. Select **Google KMS** and provide the following:
 
    <Details id="gcpApplicationProjectId" summary="gcpApplicationProjectId">
@@ -175,7 +175,7 @@ An AWS KMS Wallet is a wallet securely stored in your AWS account. Engine can cr
 1. Ensure your [keyring is created](https://cloud.google.com/kms/docs/create-key-ring) with the following settings:
    - Purpose: `Asymmetric sign`
    - Algorithm: `Elliptic Curve P-256 - SHA256 Digest`
-1. In the dashboard, navigate to **Overview > Backend Wallets**.
+1. In the dashboard, navigate to **Overview > Server Wallets**.
 1. Select **Import** and provide the following:
    - GCP KMS Key ID (example: `0489da75-9830-4a5a-97e3-e4a6df7775b3`)
    - GCP KMS Version ID (example: `1`)
@@ -189,12 +189,12 @@ An AWS KMS Wallet is a wallet securely stored in your AWS account. Engine can cr
 1. Create a Circle account at the [Circle Console](https://console.circle.com/signin).
 2. Navigate to [API & Client Keys](https://console.circle.com/api-keys).
 3. Create an API Key. (Either a standard key or a restricted key scoped to "Programmable Wallets" is required.) Do not enable the IP Allowlist. Store this key, it is not shown again.
-4. In the dashboard, navigate to **Configuration > Backend Wallets**.
+4. In the dashboard, navigate to **Configuration > Server Wallets**.
 5. Select **Circle** and provide the following:
    - API Key (example: `API_KEY:...`)
 
 <Callout variant="info">
-	Circle API Keys are scoped to either Testnet or Mainnet. Backend wallets
+	Circle API Keys are scoped to either Testnet or Mainnet. Server wallets
 	created with a testnet key will not work on the mainnet, and vice versa
 	<br /> If you want to change between testnet and mainnet, you will need to
 	update the API key configuration in engine, and recreate a wallet with the
@@ -205,7 +205,7 @@ An AWS KMS Wallet is a wallet securely stored in your AWS account. Engine can cr
 
 For AWS or Google Cloud KMS wallets, you must provide your credentials.
 
-1. In the dashboard, navigate to **Overview > Backend Wallets**.
+1. In the dashboard, navigate to **Overview > Server Wallets**.
 1. Select **Create**.
 1. (Optional) Provide a label to organize your wallets.
 
@@ -215,18 +215,18 @@ Circle wallets require creating a [Credential](/engine/features/wallet-credentia
 
 For AWS or Google Cloud KMS wallets, you must provide your credentials.
 
-1. In the dashboard, navigate to **Overview > Backend Wallets**.
+1. In the dashboard, navigate to **Overview > Server Wallets**.
 1. Select **Import**.
 1. Provide the requested fields.
    - See above for instructions for specific wallet types.
 
 ## List wallets
 
-In the dashboard, navigate to **Overview > Backend Wallets** to view your wallets created by or imported to Engine.
+In the dashboard, navigate to **Overview > Server Wallets** to view your wallets created by or imported to Engine.
 
 ## Best practices
 
 - It is recommend to use AWS or Google Cloud KMS wallets for production use. Private keys are never exposed and the wallet is backed up securely by the cloud provider.
-- Use labels and multiple backend wallets to organize and track usage.
+- Use labels and multiple server wallets to organize and track usage.
   - Example: Use one wallet to pay out creators on your platform and another to airdrop NFTs to users.
 - If your wallets require topping up gas or ERC20 tokens regularly, consider a separate "funds storage" backend wallet that transfers funds to other wallets via the dashboard UI or API.

apps/portal/src/app/engine/get-started/page.mdx

@@ -5,12 +5,12 @@ import lifecycleImage from "../assets/tx-lifecycle.webp";
 export const metadata = createMetadata({
 	title: "Getting started with Engine | thirdweb Infrastructure",
 	description:
-		"Learn how to use Engine to manage your backend wallets and call contract methods",
+		"Learn how to use Engine to manage your server wallets and call contract methods",
 });
 
 # Get Started
 
-Once you have Engine set up, learn the basics of Engine.
+Learn how to get setup and started with Engine Cloud by setting up a Vault, creating server wallets, and sending your first transaction.
 
 ## Learn how transactions work
 

apps/portal/src/app/engine/page.mdx

@@ -1,6 +1,9 @@
 import OverviewImage from "./assets/engine-overview.png";
-import { DocImage, OpenSourceCard } from "@doc";
+import { DocImage, FeatureCard, OpenSourceCard, Callout } from "@doc";
 import { createMetadata } from "@/components/Document";
+import { Activity, CircleCheck, RotateCcw, Ban, File, MessageCircle, Wallet, Blocks, ArrowLeftRight, SlidersHorizontal} from "lucide-react";
+import SupportedChains from "../_images/supported-chains.png";
+
 
 export const metadata = createMetadata({
 	title: "thirdweb Engine",
@@ -9,84 +12,85 @@ export const metadata = createMetadata({
 
 # Engine
 
-Engine is an open-source, backend server that reads, writes, and deploys contracts at production scale.
-
-## Why use Engine?
-
-Engine enables your app to:
-
-- Send multiple blockchain transactions at once.
-- Resubmit stuck transactions, handling nonce values, gas settings, and RPC errors.
-- Avoid duplicate transactions.
-- Manage multiple backend wallets and their funds.
-- Control access from your backends and team members.
-- Sponsor user gas fees.
-- Deploy and interact with smart accounts.
-- Subscribe to contract events and transactions.
-
-🚀 [Get Engine hosted by thirdweb](https://thirdweb.com/team/~/~/engine/create) or [self-host for free](/engine/self-host).
-
-### Tiers
-
-Engine is available in two tiers: Cloud and Dedicated. 
-- **Cloud**: thirdweb-hosted Engine with autoscaling and high availability.
-- **Dedicated**: Self-hosted Engine with full control over your infrastructure.
-
-
-<DocImage
-	src={OverviewImage}
-	alt="Engine overview"
-	className="max-w-[500px] mx-auto"
-/>
+Engine provides a way to read and write to the blockchain at scale through simple API endpoints.
 
 <OpenSourceCard title="Engine" href="https://github.com/thirdweb-dev/engine" />
 
-## Standard Engine
-
-Supports 500 write transactions per second. Great for minting APIs, airdrops, and managing user wallets.
-
-#### Features
-
-- <strong>High transaction throughput</strong> - Transactions batched on the same
-  block with nonces managed automatically.
-- <strong>Secure backend wallets</strong> - Your backend wallets stored locally,
-  on AWS KMS, or on Google KMS.
-- <strong>Any contract on any EVM chain</strong> - Supports contract calls on all <a href="https://thirdweb.com/chainlist">
-  	1700+ EVM blockchains
-  </a> and private subnets.
-- <strong>Contract deployments</strong> - Deploy smart accounts, tokens, NFTs, marketplaces,
-  and more.
-- <strong>Account abstraction</strong> - Use smart accounts and session keys to transact
-  on behalf of your users.
-- <strong>Built-in relayer</strong> - Sponsor gas for your users so reduce user friction.
-- <strong>Event webhooks</strong> - Get notified of wallet and contract events to
-  automate other actions like payments or emails.
-- <strong>Contract subscriptions</strong> - Store event logs and transaction receipts
-  to be queried later.
-- <strong>Transaction observability</strong> - Debug transaction failures with detailed
-  timelines, onchain errors, and gas details.
-- <strong>Idempotency</strong> - Prevent costly, duplicate transactions.
-- <strong>Production-ready web3 infrastructure</strong> - Includes RPC, IPFS, and
-  Account Abstraction out of the box.
-
-## Premium Engine
-
-Engine Premium provides added scaling and resilience. It include server autoscaling, server failover, database failover, and 30-day database backups.
-
-#### Features
-
-- **_Everything in Standard Engine_**
-- **Autoscaling** - Scale to millions of users with a fleet of Engine instances that scale up along with your traffic.
-- **Production-grade Server** - High availability and redundancy.
-- **Production-grade Database** - High availability, Multi-AZ.
-- **Database backups** - Recoverability and peace of mind for your stored data (30-day database backups).
-
-## Pricing
-
-Cloud-hosting Engine with thirdweb starts at $99 per month. Learn more about [Engine pricing](https://thirdweb.com/team/~/~/engine/create).
-
-Self-hosting Engine is always free.
+## Features
+
+<div
+	className="my-4 grid gap-2 md:grid-cols-2 lg:grid-cols-2 "
+>
+	<FeatureCard
+		title="Concurrent Transactions"
+		description="Send multiple transactions at once with automatic nonce management"
+		iconUrl={<ArrowLeftRight />}
+	/>
+
+    <FeatureCard
+    	title="Avoid Transaction Failures"
+    	description="Resubmits stuck transactions, handling nonce values, gas settings, and RPC errors."
+		iconUrl={<RotateCcw/>}
+    />
+
+    <FeatureCard
+    	title="Wallet Management"
+    	description="Manage funds and send transactions without worrying about topping up gas fees."
+		iconUrl={<Wallet/>}
+    />
+
+	<FeatureCard
+    	title="Granular Access Control"
+    	description="Control access to server wallets via access tokens with specified permission scopes"
+		  iconUrl={<SlidersHorizontal/>}
+    />
+
+	<FeatureCard
+    	title="Abstract Blockchain Complexity"
+    	description="Sponsor gas fees using built-in relayers and session keys to transact on behalf of users."
+		iconUrl={<CircleCheck/>}
+    />
+
+    <FeatureCard
+    	title="Offchain Integrations"
+    	description="Integrate with existing services to do onchain actions triggered from offchain events."
+		iconUrl={<Blocks/>}
+    />
+
+        <FeatureCard
+    	title="Programmatic Deployments"
+    	description="Deploy smart accounts, tokens, NFTs, marketplaces, and more."
+		iconUrl={<Blocks/>}
+    />
+
+    <FeatureCard
+    	title="Transaction Observability"
+    	description="Debug transaction failures with detailed timelines, onchain errors, and gas details."
+      iconUrl={<Activity/>}
+    />
+</div>
+
+## Engine Cloud vs. Dedicated
+
+<Callout variant="info" title="Engine Cloud (Beta)">
+  Engine Cloud is currently in beta as we are adding more features, endpoints, and improving performance. 
+  
+  Try it out for free by creating a project on dashboard.
+</Callout>
+
+| Feature            | Cloud ☁️                                   | Dedicated (V3), Coming Soon               |
+|--------------------|-------------------------------------------|------------------------------------------|
+| Wallets            | Server Wallets                           | Server Wallets, AWS, GCP, Circle         |
+| Database Backups   | ❌                                        | 30 Day Backups                              |
+| Infrastructure     | Shared                                   | Isolated                                 |
+| Rate Limits        | [Limited by RPC Plan](https://thirdweb.com/pricing) | Unlimited                                |
+| Pricing            | [See pricing page](https://thirdweb.com/pricing) | [See pricing page](https://thirdweb.com/pricing) |
+
+
+## Supported Chains
+
+Engine is supported on every EVM compatible chain and private subnets. To view the full list, visit [thirdweb chainlist](https://thirdweb.com/chainlist?service=engine).
+
+<DocImage src={SupportedChains} />
 
-## Get in touch
 
-For dedicated support and feature requests, [contact Sales](https://thirdweb.com/contact-us).