2
JS
JustShop Store
Project Settings
General configuration, domains, ownership, and lifecycle
General settings
Displayed throughout the dashboard.
Reference used in APIs and URLs.
Project access
Organization-wide access
All 1 organization members can access this project.
| Member | Role |
|---|---|
| [email protected] YOU | Owner |
Project availability
Restart or pause your project when performing maintenance
Restart project
Your project will not be available for a few minutes.
Pause project
Your project will not be accessible while it is paused.
Backup settings
Download or copy project environment configuration
auth.env configuration file
Contains account email, database credentials, project URL, anon key, and service_role secret.
Delete project
Permanently remove your project and its database
⚠️
Deleting this project will also remove your database.
Make sure you have made a backup if you want to keep your data.
Make sure you have made a backup if you want to keep your data.
Compute and Disk
Configure the compute and disk settings for your project.
ℹ️
Only available on Pro Plan and above
Upgrade to the Pro Plan to configure compute and disk settings.
Compute size
Hardware resources allocated to your Postgres database
NANO
$0 / hour
⚡ Up to 0.5 GB memory
🖥️ Shared CPU
MICRO
$0.01344 / hour
⚡ 1 GB memory
🖥️ 2-core ARM CPU
SMALL
$0.0206 / hour
⚡ 2 GB memory
🖥️ 2-core ARM CPU
MEDIUM
$0.0822 / hour
⚡ 4 GB memory
🖥️ 2-core ARM CPU
LARGE
$0.1517 / hour
⚡ 8 GB memory
🖥️ 2-core ARM CPU
XL
$0.2877 / hour
⚡ 16 GB memory
🖥️ 4-core ARM CPU
Disk Size
GB
Your plan includes 1 GB of disk size for gp3.
0.25 GB used of 8 GB
Database
WAL
System
Available space
Note: Disk Size refers to the total space your project occupies on disk, including the database itself (currently 0.02 GB), additional files like the write-ahead log (currently 0.06 GB), and other system resources (currently 0.16 GB). Data can take 5 minutes to refresh.
Advanced disk settings
Specify additional settings for your disk, including autoscaling configuration, IOPS, throughput, and disk type.
Infrastructure
Region routing, database host, SSL certificates, and network security
Primary Region
Integrations
Connect external payment gateways, Discord bot webhooks, and TabDeck extensions
Discord Sales Notifications Bot
API Keys
Configure API keys to securely control access to your project
⚡ Your new API keys are here
We've updated our API keys to better support your application needs. Join the discussion on GitHub ↗
Having trouble with the new API keys? Contact support
Publishable key
This key is safe to use in a browser if you have enabled Row Level Security (RLS) for your tables and configured policies.
| NAME | API KEY | ACTIONS |
|---|---|---|
|
default
No description
|
|
⋮ |
Publishable keys can be safely shared publicly
Secret keys
These API keys allow privileged access to your project's APIs. Use in servers, functions, workers or other backend components of your application.
| NAME | API KEY | ACTIONS |
|---|---|---|
|
default
No description
|
|
⋮ |
anon
public
This key is safe to use in a browser if you have enabled Row Level Security for your tables and configured policies. Prefer using Publishable API keys instead.
service_role
secret
This key has the ability to bypass Row Level Security. Never share it publicly. If leaked, generate a new JWT secret immediately. Prefer using Secret API keys instead.
Disable legacy API keys
Make sure you are no longer using your legacy API keys before proceeding.
JWT Keys
Control the keys used to sign JSON Web Tokens for your project
CREATE STANDBY KEY
Set up a new key which you can switch to once it has been picked up by all components of your application.
| STATUS | KEY ID | TYPE | Actions |
|---|---|---|---|
| ✓ CURRENT KEY | 064R3RZUF6YGE1D194PG8Q0BNBJEZQIA | 🔒 ECC (P-256) | ⋮ |
Previously used keys
These JWT signing keys are still used to verify tokens that are yet to expire. Revoke once all tokens have expired.
| STATUS | KEY ID | TYPE | LAST ROTATED AT | Actions |
|---|---|---|---|---|
| ↺ PREVIOUS KEY | 064R3RZUF7YGE1D194PH8Q0BNBJEZRIA | 🔒 Legacy HS256 (Shared Secret) | 3 months ago | ⋮ |
⚠️ Legacy JWT secret has been migrated to new JWT Signing Keys
Changing the legacy JWT secret can only be done by rotating to a standby key and then revoking it. It is used to only verify JSON Web Tokens by Supabase products.
This includes the anon and service_role JWT based API keys. Consider switching to publishable and secret API keys to disable them.
Used only to verify JWTs.
How long access tokens are valid for before a refresh token has to be used. Recommendation: 3600 (1 hour).
seconds
Log Drains
Stream API request logs, database queries, and webhook events to external log services
Custom Log Drain Destination
Add-ons
Enable TabDeck modules, custom domain routing, and AI copilot services
TabDeck Desktop & Dock Extensions
Enable seamless sync with TabDeck Chip Store, Dock App Store, and Server App Store.
Data API
BetterBase REST and GraphQL API endpoints, rate limits, and CORS rules
REST API Endpoints
Vault BETA
Encrypted secret storage for payment API keys and private merchant credentials
Store Secret Vault
All secrets stored here are encrypted with AES-256-GCM.
Subscription
Merchant organization plan, billing details, and active storefront quotas
Current Organization Plan
Pro Merchant + BetterBase DB Bundle
1:1 Linked BetterBase Postgres Project ID:
proj_f96f3d_db
Includes Unlimited Storefronts (Amazon, TikTok, Merch, Dock App, Server App, Chip), 100GB Storage, 1M API Requests/month, and Dedicated Postgres Compute.
Database Membership Lifecycle & Freeze Policy
How your 1:1 BetterBase database subscription interacts with your JustShop merchant account:
1. Paid Tier (1:1 Active)
Merchant profile is linked 1:1 to BetterBase org. Full Postgres compute, REST API, publishable & secret keys active.
2. Unpaid (30-Day Freeze)
If subscription is unpaid, database is FROZEN for 30 days. JustShop storefront stays active; DB queries are paused.
3. Post 30-Day Deletion
After 30 days without payment, Postgres DB instance is deleted. JustShop storefront remains active without database.
Payment
Configure payout settings, currency, connected payment gateways, and crypto wallet addresses.
Currency
Threshold
The payment will be automatically accepted if it is within the % range.
012345678910
Usage Statistics
Real-time resource utilization, database size, API request quota, and bandwidth
Monthly Resource Consumption
API Requests: 14,820 / 1,000,000 requests
Database Storage: 142.5 MB / 100 GB
Bandwidth Transfer: 4.82 GB / 500 GB