What is Struxel Dynamics?

Struxel Dynamics manages 5 data types including demo analytics events. Helps you organize, track, and share your work in 1 place for teams and solo users.

Self-Hosted Deployment

Self-Hosted Launch Wizard

Onboarding and migration orchestrator for self-hosted Struxel deployments.

⚠ No workspaceId in URL — open via the link your SE sent you.

Infrastructure

Product Endpoints

Delivery Mode

Validation

Go-Live Handoff

Phase 1 — Infrastructure / Network

These values match what is in your Terraform plan. If you haven't run Terraform yet, your SE will provide them after the initial infrastructure review.

Base Domain *

Root domain for your Struxel deployment (e.g., ai.yourcompany.com)

VPC ID

AWS VPC where your ECS cluster runs

Subnet IDs

Comma-separated list of subnet IDs for ECS tasks

ACM Certificate ARN

ARN of your TLS certificate for the ALB

Route 53 Hosted Zone ID

Zone ID for your domain in Route 53 → Hosted zones

Live Architecture Preview

Live Architecture Preview · updates as you type

🌐 Internet · ai.yourcompany.com

⬡ Route 53 A-Alias · A → ALB

🔷 VPC — vpc-xxxxxxxx

⚖ Application Load Balancer · HTTPS:443 · ACM TLS

Private Subnet 1 · subnet-aaa

◈product-service-1:8080

◈product-service-2:8080

◈product-service-3:8080

Private Subnet 2 · subnet-bbb

◈product-service-1:8080

◈product-service-2:8080

◈product-service-3:8080

🛢 RDS PostgreSQL · governance_db · Multi-AZ

Secrets Manager

License key injection

DB credentials

prefix: struxel/tenants/

CloudWatch

Log groups per service

Alarms → SNS

/struxel/{tenant_id}/logs

Readiness Checklist

0/19 complete · 0%

IAM Role created

StruxelDeploymentRole with trust policy

ECR cross-account pull granted

SE confirms allowlist for your account ID

VPC identified

VPC ID noted with 2+ public & private subnets

Subnet IDs collected

At least 2 private subnets for ECS tasks

NS Delegation done

Subdomain NS records delegated to Route 53

ACM Certificate issued

Wildcard or specific cert for your domain

Hosted Zone ID noted

From Route 53 → Hosted Zones

Secrets store configured

AWS Secrets Manager, Vault, or .env ready

License key received from SE

Stored securely before deployment

Database credentials ready

PostgreSQL connection strings prepared

Terraform initialized

terraform init completed without errors

tenant-bundle.json downloaded

Generated and verified in Phase 4

terraform.tfvars populated

All variables filled from bundle + infra

Terraform apply completed

No errors in apply output — check ECS service stability

Health endpoint returns OK

GET /api/health → {status:'ok'} and /api/license → {valid:true}

Smoke test passed

Rollback plan documented

Previous image tag noted — terraform apply with prior tag reverts instantly

SE health verification done

All services healthy in TES workspace — SE signs off

CCC workspace unlocked

SE marks go_live_verified in portal — customer receives access email

📋 Readiness Checklist