Google Cloud
Connect a Google account, choose a workspace project and review the access available to your team.
TWO SPADES / MISSION CONTROL
Command your cloud.
Deploy an environment. Clone a proven setup.
Keep every step of the mission in view.
CLOUD OPERATIONSMODE / AWAITING STATUSWRITE GATE / LOCKED
Setup required
01 / CONTROL LINK GOOGLE CLOUD
Link your cloud.
Connect your Google Cloud project to prepare the next deployment.
02 / COMMAND INTERFACES
Three ways.
One command.
The dashboard, API and ChatGPT use the same deployment engine.
0Environments
0Deployment jobs
—Application templates
0Jobs in progress
Environments
A clear view of where your apps live.
Operations log
The actual progress behind every launch.
YOUR APPLICATIONS
Environments
Every environment has its own resources and a traceable app commit.
EVERY STEP, IN VIEW
Deployments
Provisioning, workflow dispatch and application acceptance stay distinct.
LESS REPETITION. MORE MOMENTUM.
Launch from a template.
Reusable infrastructure, ready for your next environment.
YOUR WORKFLOW. CONNECTED.
One engine.
Every interface.
Use SpadePilot in the way that fits the work.
REST API
Prepare plans, start jobs and inspect progress from your own services and automations.
ChatGPT MCP
Ask for the same operations from your conversations using the SpadePilot MCP server.
TWO SPADES / DOMAINS
Give your projects
a home.
Review DNS changes, preserve existing records and follow the actual result.
Namecheap
Connection setup
The service owner connects Namecheap on the server and whitelists its fixed outbound IPv4. Credentials stay on the server. Existing nameservers and email settings are retained.
Review the exact changes
Check every removal and destination before applying. Other DNS records are preserved. Changes made at Namecheap after this review require a fresh plan.
DNS operations
DNS records verified means Namecheap holds the reviewed records. Propagation, valid HTTPS and authenticated service checks are separate.
Preview the coming soon page ↗TWO SPADES / AI OPERATIONS
AI costs.
Actual OpenAI charges and the work behind them.
Provider billing meets Questions Storm activity.
CSV snapshotUSD · UTC BILLING DAYS
Loading this workspace’s cost evidence…
No cost snapshot yet.
Ask a workspace owner or admin to import an OpenAI Cost data CSV. Nothing is assumed to be free.
RECORDED SPEND ACTUAL
—Provider-recorded usage charges, before tax.
IMAGE EDITING / OPENAI
—Source images + prompt inputs + generated images.
QUESTIONS STORM / WORKFLOW EVIDENCE
—Reported runs
—Generated outputs
—Unique questions
—Applied by these runs
Where the spend went.
ACTUAL / USDDaily flight log.
UTC DAYS| Billing day | Runs | Outputs | Actual spend |
|---|
Billing follows the provider’s UTC day. Runs follow their start timestamp; a run spanning midnight stays on its start date.
The work behind the numbers.
INTERNAL / SAVED RUNS| Run / started UTC | Selected | Outputs | Applied | Requests | Reserved USD | Review |
|---|
Workflow request reservations —Ledger-recorded requests —
Reservations are spending controls, not provider charges. Account totals are not allocated to individual runs. Ready/partial outcomes do not establish editorial acceptance.
SOURCE / RECONCILIATION
Snapshot captured ·
Account costs by day. Individual workflow allocation is approximate. Automatic billing sync is not connected.
Inspect provider billing line items
| Model / billing line | Recorded USD |
|---|
SPADEPILOT / ESTABLISH YOUR WORKSPACE
Your client.
Your cloud.
Create a workspace, connect Google and choose where the work belongs.
Ownership, access and billing stay in view.
Design preview · explore the setup layout. Google sign-in, workspace changes and cloud operations are disabled.
- Workspace
- Hosting route
- Target & payer
- Review
- Verify
WORKING ON YOUR REQUEST…
You have a workspace invitation.
YOUR ACCOUNT
Start with your Google account.
Checking sign-in availability…
Continue with Google ↗01 / WORKSPACE
Who is this project for?
Keep each client's projects, people and activity in their own workspace.
02 / HOSTING ROUTE
Where will the work live?
Connect the client's existing Google project, or create an empty project in an authorized organization. Your workspace's ownership and payer choice remain visible throughout.
This creates no Google account, payment profile or server. Client-owned, client-paid is the default; managed hosting is an explicit workspace choice.
03 / GOOGLE CONNECTION
Connect the account with access.
04 / TARGET AND PAYER
Use a project you already have.
Connect a project where the selected Google account has access. Its ownership and billing stay in place.
Create an empty Google project.
Use the client organization or folder where this account has permission. Creating a project does not grant Two Spades access automatically.
Set up billing with Google ↗ · Return here after completing Google's account or billing steps.
05 / REVIEW SETUP
Know exactly what happens next.
06 / VERIFY YOUR SETUP
Know where you are working.
Your connected projects will appear here.
A connected Google project is ready for workspace administration. Client application templates and deployment verification need a separate release before this workspace can launch an environment.
Open workspace cockpit ↗Manage people, API access and activity
PEOPLE AND ACCESS
Invite the right people.
Invite a client administrator or colleague. Workspace membership does not automatically grant Google permissions.
| Member | Role | Access |
|---|
API access for this workspace
Keys stay bound to this workspace and the issuing member's current role. They expire after 90 days.