Client Portal
Customer sign-in, billing, guides, support, integrations, and workspace links.
Live sign-inOpen ↗
Staging reviewOpen ↗
Command Center
Own the Stack
01
Access Directory
One place for every current Own the Stack sign-in, service, and operating dashboard. This page stores links only—never passwords, recovery codes, or API keys.
Team Portal
Customer records, fleet, signups, billing, and internal support work.
Live team sign-inOpen ↗
Fleet boardOpen ↗
Website & Checkout
Public service information and the standard customer purchase flow.
Own the StackOpen ↗
Start / checkoutOpen ↗
Operations Status
Live working record, red/yellow priorities, and operational links.
Tools & SoftwareOpen ↗
Tech HubOpen ↗
02
Current Status
Live operating picture. Red needs immediate attention, yellow needs proof or a decision, and green is working.
No active outage recorded
There is no reported service failure in the current record.
- Escalate any down monitor, stale backup, certificate warning, or broken portal check immediately.
Three items need completion
These are active validation items, not service failures.
- Invoice and receipt history must appear in the correct portal record.
- Manual-payment results must connect to that same portal record.
- A real scheduled renewal still needs observation.
Core service is working
Provisioning, monitoring, portal access, and workflow reporting are active.
- Customer workspace setup and infrastructure monitoring are operating.
- Client and Team Portal browser checks run on a six-hour cadence.
- Workflow results are reporting into the portal for review.
03
Roadmap
Current work, then the next proof.
Show the paid invoice and receipt in the correct client portal.
Connect the approved invoice path to that same portal record.
One record and SOP for client requests and automatic failure response.
04
View All Changes Recent Changes
Latest verified project movement.
Carl’s publisherCarl’s Notion-to-Substack publisher is live and operating normally. Scheduled posts are now in observation mode; the read-only portal sync continues to report the workflow’s last run and result without changing n8n.
Workflow inventoryCarl’s portal record now holds the two workflow names his n8n workspace reports. The sync is read-only; it does not change n8n. The client page is wired to show only the signed-in customer’s own inventory, with one visual client-page proof still open.
Billing gapThe active subscription and renewal date are linked; invoice and receipt history is still empty in the client portal.
Manual paymentsGHL/FastPayDirect invoice links are available for collection, but they are not yet connected to portal billing records.
Email guardrailNo new Resend sender, alert recipient, automated email, or delivery test is permitted without Kimi’s explicit approval. The qa-relay alert burst is verified stopped (11:47 PM, October 12) and deleting a workspace now restarts Uptime Kuma so a removed monitor cannot keep sending. Every Resend sender is listed on the Tech Hub Servers page.
Ticket systemClient requests and technical failures do not yet share one tracked record, n8n trigger, team workflow, and client-visible status.
Change history
- October 13 (Claude): Carl’s Notion-to-Substack automation went live at 8:29 PM. The n8n workflow “Carl - Notion Substack Publisher (MVP)” publishes a Substack Publishing Queue post when Status is Approved, Integration Status is Ready, and the Publish Date has arrived, emails subscribers, and writes the Substack Post ID and URL back to Notion. The first post, “Founders School Is Betting $600K…,” published with its header image. Substack has no official connection, so a standalone Python runtime, the substack-cli tool, and the publishing script were installed in the n8n storage volume on Carl’s server (no image change, no restart). Carl’s Substack sign-in code lives in one file on his server and expires every 2 to 4 weeks; refreshing it is not automated yet. The portal workflow inventory picked it up at the 8:29 PM sync and shows it as active. The earlier archived draft was permanently deleted at Kimi’s request, so the portal now lists only the live workflow. The 15-minute portal workflow sync now also reads each workflow’s last run time and result from n8n (read-only, all clients), so the portal’s Last run column shows real values.
- October 12: the workflow inventory sync and team-side Automations tab were deployed. The read-only n8n response for Carl reports two saved workflow records; no workflow was created, edited, activated, run, or deleted.
- October 12: the six-hour portal browser checks, screenshot capture, report intake, and Tech Hub reporting passed their first live run.
- October 12: Stripe webhook metadata proved the active subscription and renewal date can reach the correct portal record.
- October 12: invoice/receipt display and the manual-payment handoff were identified as the active billing work; the old portal-walkthrough status is no longer the immediate priority.
05
Documentation & Resources
The working documents are here in the original document-board format.
Build Specification
The developer implementation plan for infrastructure, provisioning, portals, backups, monitoring, security, and launch phases.
Updated 15 September 2026Client Service Agreement
The business, pricing, restoration, backup, and Florida jurisdiction details are filled in. The agreement is live as the GHL terms step and linked from the required checkout acceptance checkbox.
Updated 28 September 2026Manual Provisioning and Recovery Runbook
Jason's audited manual provisioning and recovery process, including post-pilot security, monitoring, notification, backup-freshness, and OS-update verification.
Audited 30 September 2026Dr. Hall Workflow 1 Roadmap v1.1
The current content-workflow plan covering YouTube, OpusClip, approval branches, and draft-only WordPress and Wix outputs.
Latest workflow update 8 October 2026Source attachment retained in the internal project record
How the service works
Part 1
The four pieces
Customers only ever see the two pieces on the top row. The bottom row is internal, one for the team's eyes, and one that nobody sees because it's the machinery doing the work automatically.
Customer uses
Their Workspace
tracy.ownthestack.ioThe customer's own private automation studio (n8n, under its own name). Their login, their workflows, their connected apps. No other customer can see it or touch it. This is the thing they're renting a managed home for.
Customer uses
The Client Portal
portal.ownthestack.ioThe "front desk" of the business. One button opens their workspace; the rest is account information, billing, how-to guides, and submitting a request when the team is needed.
The team uses
The Team Portal
portal.ownthestack.ioThe team signs into the same portal and receives the protected team view. It is mission control for every customer: workspace health, backup age, payment status, new signups, and open requests. Green means "do nothing." That's the low-touch part.
Runs itself
The Machinery (invisible)
Software the developer builds once, then it works around the clock: it builds each new customer's workspace after payment, takes the nightly backups, checks every workspace every minute, and pauses accounts that stop paying. This is what makes it a business instead of a job.
Part 2
One customer's journey, start to finish
This is the intended customer journey. Steps marked Automatic describe the intended customer experience. Current work and proof remain in the status and roadmap above.
-
1
Tracy signs up and pays Tracy
She picks a plan on the website and pays with her card. That's the last required human action in the whole setup.
-
2
Her workspace is built Automatic
Within about ten minutes the machinery rents her a dedicated server, installs her private workspace, gives it its address (tracy.ownthestack.io), locks it down, and signs her up for backups and monitoring.
-
3
Welcome email arrives Automatic
Her workspace address, how to set her password, a link to the client portal, and a plain one-pager: what the subscription covers, and how to ask for help if she ever wants it.
-
4
Tracy builds her automations Tracy
She (or anyone she chooses) builds whatever she wants in her workspace. Nobody on the team touches her workflows, the subscription is for keeping the lights on, not for what she builds under them.
-
5
Months pass quietly Automatic
Backups every night. Health checks every minute. Security updates on schedule. If her workspace ever goes down, the team gets an alert, usually before she notices. She just sees that it always works.
-
6
Something breaks, or she wants something new Tracy's choice
An app update breaks one of her automations, or she dreams up something she can't build herself. Now she has three doors, see below. Which one she opens is entirely up to her.
Part 3
The three doors, help is optional, always
The subscription never requires her to use the team. All three doors are legitimate, and the portal says so out loud.
Door 1
Do it herself
It's her workspace with full access. She can build, fix, and change anything on her own, forever, at no extra cost.
Door 2
Hire anyone she likes
Her own employee, a contractor, a freelancer, anyone she trusts can work in her workspace. There is no charge for that and nothing standing in the way.
Door 3 · Optional implementation
Ask the team
One request in the portal. Optional implementation is quoted separately after the team reviews the customer's software, setup, and scope. No fixed starting price is published, and the team confirms the quote before work begins.
Why Door 3 wins anyway: it never has to be forced. When the company that keeps her server running, holds her backups, and already has vetted engineers is one ticket away, most customers pick that door on their own, because it's the easiest one. That convenience is the product. The other two doors staying open is what makes customers comfortable walking in at all.
Part 4
Who does what
The clean line that keeps the subscription low-touch and keeps expectations straight from day one.
Covered by the subscription
The promise, mostly delivered by the machinery
- A private, dedicated workspace of their own
- Secure hosting and security updates
- Nightly backups, kept safe off-site
- Round-the-clock monitoring and alerts
- Software updates, tested before rollout
- Account and billing management
Not covered, quoted separately when requested
The customer's work, with optional implementation available by quote
- Building automations and workflows
- Fixing a workflow that stopped working
- Connecting new apps and APIs
- AI prompt writing and tuning
- Training, consulting, strategy
- Ongoing workflow management