VibeStudio help › All pages

VibeStudio help

Index

Tabs

Build Adopter BE Code Build

Complete Core BE Build

DNS Provisioning

Deploy Mkting Web

Deploy SaaS App

Email

Framework authority

Help

Install Dev tools

Monitoring

Purchase Dev Tools

Rebuild It

Set Up New Project

Status Info

Stripe

Test

Tunde

Tune

Settings

Account Alias

Any Extra Rules

App Title

Bucket Prefix

Domain (e.g. myapp.com)

Email Provider

Emails/Day at 6 Months

Emails/Day at Launch

Entity List

Framework Dev Repo (framework author only)

Git User Name

Legal Company Name

Licensed Modules

My NEW Git Repository Name

Privacy Policy URL

Product Name

SES Contact Email

Secret Name Prefix

Sender Email

Stripe Mode

Stripe Publishable Key

Trial Token Grant

User Description

Web Content Folder

Steps

AFTER A WIPE: — Put back data and connections

Ask AWS for the approvals a new account needs

Associate the app.* address with the Amplify app

Associate your domain and www with the website's Amplify app

BEFORE YOU REBUILD: — Look at what is deployed

BUILD AND DEPLOY: — Core stack, then your product's back end

Build the app for publishing (npm run build, into dist)

CU1 — Disassociate app.<domain> from Amplify

CU2 — Delete the marketing CloudFront distribution

CU3 — Delete the SaaS Amplify app

CU4 — Empty and delete the app S3 bucket

CU5 — Empty and delete the marketing S3 bucket

CU6 — Delete ACM certificates

CU7 — Delete Route 53 hosted zones

Check AWS state and choose the rebuild path

Check SES production access status

Check Stripe still reaches this deployment

Check Tool Versions

Check before release

Check every help link has its page

Check the HTTPS certificates will keep renewing

Check the front end is in place

Choose where your help pages live

Choose your Repository Folder (shared by every product)

Copy API Gateway ID into public/apiconfig.adopter.json

Copy API Gateway ID into public/apiconfig.json

Copy existing DNS records — from your registrar

Create Route 53 — hosted zones for apex, app.*, and www.*

Create SAM deployment S3 buckets (if missing)

Create a Resend account and add your domain

Create admin_account customer and admin user

Create the API domains — and point them at the stacks

Create the Amplify app from the S3 bucket

Create the app's S3 bucket

Create the sign-in (JWT) secret

Create the website's Amplify app from the S3 bucket

Create the website's S3 bucket

Create, Build and Deploy vibe-core

Cut a Framework Release — (responsibility of framework authority)

Cut a release

DNS PROVISIONING: — Set up subdomains, certificates, and DNS routing

Email1 — Verify email addresses used for testing

Email2 — List email addresses that can be used for testing

Follow the Adopter Setup Guide

INSTALL DEV TOOLS: — Check, install and update the tools on this PC

Install / Upgrade npm

Install Git

Install GitHub CLI (gh)

Install Node.js

Install Python 3.13

Install Visual Studio Code

Install or Update AWS CLI

Install or Update SAM CLI

Install the front end's packages (npm ci)

Merge a Framework release into your product's code

Merge finished work into main — (responsibility of framework authority)

Name your product and your GitHub account

Only for CloudFront hosting: — request the website's ACM certificate

Only for CloudFront hosting: — wait for the certificate

Only for CloudFront hosting: — write its validation records

Open the bare domain in your browser

Open the live website (www) in your browser

PHASE 1: — Prepartions and Prerequisites

PHASE 3: — Optionally Test several back end functions for vibe-core

PHASE 6: — Deploy / Re-deploy Back End of My SaaS: to AWS

PHASE 6:Infrastructure

PHASE 7:Performance

PHASE 8:Monitoring and Backup

PHASE 9: Security

PHASE: Live Site Verification — Confirm the deployed app and marketing site work end-to-end

PHASE: Tune & Polish — Fine-tune CloudFront, Amplify, env vars, error pages, and analytics

PUBLISH THE APP: — Stage it in S3, publish it with Amplify, and give it its app.* address

Point Stripe's webhook at this deployment

Protect1a — Enable DynamoDB Point-in-Time Recovery (PITR)

Protect1b — Enable S3 Versioning & Bucket Policies

Protect2a — Set Up CloudWatch Alarms for errors & spend

Protect2b — Move Secrets to AWS Secrets Manager

Protect3a — IAM Least-Privilege Audit

Protect3b — Enable AWS Cost Budget Alerts

Publish Resend's DNS records

Push content changes to the live website

Put a release in the release folder

RELEASES: — Production deploys come from the release folder

Register your website's domain name

Request SES production access (production accounts only)

Request the API certificate — (api.* and product-api.*)

Restore the trial token grant

Review Existing AWS Deployments

Run Adopter Setup — write CLAUDE.md and SPEC.md from templates

Run GITList1 — List all the checkins for a source code file

Run SAM build on your product's back end

Run SAM build to prep code for deploy

Run SAM deploy to put your product's API in your AWS account

Run SAM deploy vibe-core API to AWS account

RunWeb1 — Start the Marketing Web site

Save the token payment configuration

Send alarms to someone who will read them

Send delivery results back to this deployment

Send test emails

Set the product name in branding.js

Set up a Claude AI account

Set up a GitHub account

Set up a Stripe account for card payments

Set up an AWS account

Set up this product's AWS account

Set up your own private GitHub repo, seeded from the Framework

Show nameservers for — customer's registrar

Sign the GitHub CLI in to your GitHub account

Start the app on your PC (npm run dev)

Step D1 — Install and Start Docker (optional Debugging or skip to Step Core11)

Step D2 — Run Lambda functions locally using Docker (optional Debugging or skip to Step Core11)

Step MySaaS-? — .'(FUTURE) Run One of Your SaaS lambdas using docker with a test record. (optional Debugging or skip to Step 10)

Store Stripe keys for token purchases

Store the Anthropic API key in this AWS account

Store the Resend keys in this AWS account

TEST THE APP: — On your PC (sign in, add users and roles, and the other app pages)

Test1 — Open the app and verify the login page loads

Test2 — Open the marketing site and verify it loads

Test3 — Click Sign Up and verify it reaches the app signup page

Test4 — Create a test account

Test5 — Log out and log back in with the test account

Tune1 — Review CloudFront cache TTLs

Tune2 — Review Amplify build settings

Tune3 — Set environment variables and secrets

Tune4 — Upload custom error pages

Tune5 — Wire up analytics

Update Settings - Domain, Bucket, App Title, Web Content Folder

Upgrade the 'pip' development tool

Upload the built app (dist) to the S3 bucket

Upload the website's content to the S3 bucket

Verify NS delegation — is live in public DNS

Verify core code matches the Framework release

Verify payments reach this deployment

Verify the app's S3 bucket was created

Verify the website's S3 bucket was created

Wait until the app's address is live

Wait until the website's addresses are live

Write and review your help pages

pip install -r src/requirements.txt (python packages)

⚠️ List DynamoDB — Tables — review before any action

🟠 TEARDOWN PHASE — Remove this deployment's AWS resources for testing iteration

🟢 PROTECT PHASE — Harden security & preserve data

Generated from VibeStudio's own text.

This page was generated from the description shown inside VibeStudio. Expand it with the detail an adopter needs — what to do, what good looks like, and what to check when it goes wrong.