SkyePay is how clients continue after preview.

I built SkyePay so client app previews do not end in an unmanaged payment link. The client chooses the lane, Stripe handles Checkout, FS27 keeps the order record, and activation stays owner-approved before the workspace unlocks.

Open SkyePay Use Billing Form API Docs Scanner Proof

What is public knowledge now

Payments route through our own gateway.

Client continuation

After a private preview, clients continue through a named offer with visible setup, monthly price, included usage, request limits, and activation terms.

Owner approval

Payment does not automatically unlock a managed workspace. FS27 keeps the order pending until the owner approves activation and writes the plan policy onto the customer record.

Stripe backed

Card handling remains inside Stripe Checkout. SkyePay owns the route, offer metadata, order status, and workspace handoff state.

Callable API

Apps can call offers, checkout, and status routes directly through the SkyePay API contract and browser SDK; customer access still routes through FS27 limits.

Starter Command

$997 setup + $297/mo

$250 monthly AI cap, 30 rpm, 600 requests/day, 2 devices/key, 1 workspace, 1GB vault, 250 files.

Continue through SkyePay

Growth Cabinet

$2,500 setup + $797/mo

$750 monthly AI cap, 90 rpm, 2,500 requests/day, 5 devices/key, 3 workspaces, 5GB vault, 1,200 files.

Continue through SkyePay

Autonomous Office

$5,000 setup + $1,497/mo

$1,500 monthly AI cap, 180 rpm, 6,000 requests/day, 12 devices/key, 8 workspaces, 20GB vault, 5,000 files.

Continue through SkyePay

Managed Gate

$12,500 setup + $1,250/mo

$1,250 monthly AI cap, 120 rpm, 5,000 requests/day, 8 devices/key, 5 workspaces, 10GB vault, 2,500 files.

Continue through SkyePay