BoalTech Admin

0Deployments

0Active

0Clients

0API keys

Server Metrics

Service Metrics

Service	Status	CPU	Memory	Network

Recent Deployments

Hostname	Client	Status	Template

Templates

Deployments

Hostname	Client	Workspace	Status	Template	Container	Billing	Actions

Clients

ID	Name	Type	Contact	Status	Tokens	Billing	Updated

Workspaces

ID	Name	Client	Status	Domain	SSO	Apps	Updated

Workspace Apps

Infrastructure Nodes

ID	Name	Role	Endpoint	Status	Capabilities	Updated

Managed Infra Services

ID	Type	Name	Node	Client	Endpoint	Status	Updated

Network Sites

ID	Name	Client	Router	WANs	Subnets	VPN	Bonding	Status

Infrastructure Runbooks

Operator Guide

Onboarding New Infrastructure and Services

Use this flow whenever a new server, VPS, Proxmox host, storage node, edge proxy, VPN endpoint, or managed service is added to BoalTech.

Classify the asset as edge, VPN, worker, Proxmox, storage, mail, app host, or customer site.
Prepare the host with OS updates, SSH access, firewall baseline, monitoring, Docker if needed, and backup notes.
Register the asset in Infrastructure Nodes with hostname, public/private IPs, role, and capabilities.
Register any managed service attached to it, such as Headscale, WireGuard, OpenMPTCProuter, Traefik edge, BIND, mail, or storage.
Attach customer-facing network locations under Network Sites when the asset belongs to a client or reseller deployment.
Verify DNS, TLS, routing, health checks, access control, and rollback notes before marking production-ready.

Reseller Network

OpenMPTCProuter Site Onboarding

Use this flow for the reseller location that needs WAN bonding, failover, and remote administration through BoalTech infrastructure.

Collect WAN count, ISP names, modem handoff type, static IP availability, LAN subnet, VLAN needs, and expected throughput.
Create or select a VPN/bonding backend service in Managed Infra Services.
Create a Network Site for the reseller location with router type openmptcprouter, WAN count, LAN subnets, VPN service, and bonding service.
Install the OMR router at the site, configure each WAN independently, then attach tunnels to the BoalTech endpoint.
Validate failover by disconnecting one WAN at a time, then validate aggregation with download, upload, latency, and packet-loss checks.
Document emergency bypass, local admin access, tunnel credentials, and any static route exceptions.

Candidate Node

Home Proxmox Storage and HA Node

This node should be treated as a non-production candidate until the crash pattern is resolved. It may still be valuable as a local storage, Home Assistant, Nextcloud NAS, and lab-services node.

Register it as role proxmox or storage with status planned or maintenance.
Capabilities can include homeassistant, nextcloud, nas, ssd-array, lab, and backup-target.
Do not place customer production workloads on it until kernel logs, SMART data, thermals, RAM, power, and storage health are checked.
Best first use: private admin mesh access, local backups, lab validation, and non-critical sync targets.

Migration Runbook

Proxmox to BoalTech Control Plane

Use this when collapsing a Proxmox node into standalone Docker services managed by BoalTech. Move one service at a time, keep source backups untouched, and only decommission Proxmox after restore tests pass.

Inventory every VM/LXC: hostname, IP, purpose, storage paths, ports, domains, DNS, databases, secrets, cron jobs, backups, and dependent services.
Mark each workload as retire, keep standalone, convert to Docker, rebuild from template, or migrate later.
For each LXC, stop writes, snapshot or vzdump it, export app data from /var/lib, /etc, web roots, databases, and mounted volumes.
Create a Docker image only when needed: use pct mount or an extracted backup rootfs, then import with tar -C rootfs -cpf - . | docker import - service-name:legacy. Prefer a clean Dockerfile when the app is standard.
Move persistent data into standard host paths such as /var/lib/boaltech/<service>, with secrets in environment files or the control-plane registry.
Create a BoalTech template or deployment record with ports, volumes, env fields, health checks, DNS, Traefik labels, SSO settings, and backup notes.
Launch on a staging hostname, restore data, verify application login, DNS, TLS, mail, webhooks, uploads, backups, and rollback.
Cut over DNS or proxy routing, watch logs, then leave the Proxmox source powered off but recoverable until the next backup cycle succeeds.

Vendor Sales

Vendor Marketplace Onboarding

Use this flow for remote vendors launching at <storename>.boal.tech or their own custom domain. Public intake lives at vendwith.boal.tech.

Create or confirm the client profile, billing contact, and preferred vendor admin email.
Collect vendor name, mission, tagline, product category, public location, logo, and social links.
Choose Startup Mode for gallery/inquiry launch or Growth Mode for cart, checkout, coupons, gift cards, and order tracking.
Collect product names, descriptions, images, prices, availability, fulfillment rules, and sale/coupon details.
Confirm public phone/email visibility; default both to hidden unless the vendor opts in.
Connect BoalTech SSO, payment provider, domain, HTTPS, contact form, event calendar, and test order/inquiry before launch.

Quick Intake

Details To Capture Before Adding a Node

Node name, hostname, location, owner, and purpose.
Public IP, private IP, LAN subnets, VLANs, and gateway.
CPU, RAM, storage layout, virtualization platform, and UPS status.
Access path: SSH, Proxmox UI, VPN, out-of-band, or local only.

Services running now and services planned later.
Backup role, restore process, and retention requirements.
Customer impact if offline and whether unlimited billing applies.
Known risks, maintenance windows, and rollback notes.

Token Billing

PayPal Billing Provider

disabled

PayPal Platform Provider

disabled

Vendor Payment Accounts

Vendor	Client	Deployment	Status	Merchant	Email	Receivable	Updated

Balances

Client	Name	Balance	Status	Billing

Purchase Requests

Client	Provider	Status	Tokens	Amount	Created

Ledger

Client	Type	Amount	Balance	Memo	Created

API Keys

ID	Client	Status	Scopes	Last used

Login Accounts

Admin accounts use BoalTech SSO. Client accounts can stay Google-bound for customer portal convenience until client SSO is fully migrated.

Email	Role	Client	Provider	Status	API Key	Last used

Vendor Intake

Open intake page

Vendor	Contact	Store	Package	Products	Status	Email	Created

Custom Domains

Domain	Client	Status / Verify	Target	Registrar	Owner	Nameservers	Updated / Checked

Templates

Quick Vendor Mail

Creates a vendor mailbox on vendors.boal.tech and links the same identity into BoalTech SSO. Use SSO Webmail for browser login after the mail SSO bridge is configured.

Mail Domains

Domain	Client	Status	Updated	Error

Mail Accounts

Email	Client	Mail	SSO	Display name	Updated	Error

Mail Aliases

Use this later to deliver custom-domain mail into the quick-launch vendor mailbox.

Alias	Target	Client	Status	Updated	Error

Site Packages

Imports

Hostname	Client	Status	Archive	Image	Created / Completed	Error

Exports

Hostname	Client	Status	Size	Created / Completed	Error

Admin Console

Server Metrics

Service Metrics

Recent Deployments

Templates

Deployments

Clients

Workspaces

Workspace Apps

Infrastructure Nodes

Managed Infra Services

Network Sites

Infrastructure Runbooks

Onboarding New Infrastructure and Services

OpenMPTCProuter Site Onboarding

Home Proxmox Storage and HA Node

Proxmox to BoalTech Control Plane

Vendor Marketplace Onboarding

Details To Capture Before Adding a Node

Token Billing

PayPal Billing Provider

PayPal Platform Provider

Vendor Payment Accounts

Balances

Purchase Requests

Ledger

API Keys

Login Accounts

Vendor Intake

Custom Domains

Templates

Quick Vendor Mail

Mail Domains

Mail Accounts

Mail Aliases

Site Packages

Imports

Exports