Skip to content

docs: propose a one-click self-host option in the README - #94

Closed
vikasprogrammer wants to merge 8 commits into
trycompai:mainfrom
vikasprogrammer:adr-one-click-self-host
Closed

docs: propose a one-click self-host option in the README#94
vikasprogrammer wants to merge 8 commits into
trycompai:mainfrom
vikasprogrammer:adr-one-click-self-host

Conversation

@vikasprogrammer

@vikasprogrammer vikasprogrammer commented Aug 8, 2026

Copy link
Copy Markdown

Following CONTRIBUTING.md — this is a proposal in adrs/, not a code PR. One file, no changes to anything that runs.

Short version: we packaged the CRM as a one-click deploy and it's live. We'd like a "Deploy on InstaPods" button in the README, and we'll pay 20% of the recurring revenue from anyone who signs up through it. Happy to hear no.

You can try it before deciding anything: https://app.instapods.com/dashboard/pods/create?app=crm

It builds from source at a pinned commit and runs all four processes on one machine — PostgreSQL 17, the Nest API on Bun, the Next app, and the eve agent — behind one hostname with HTTPS. Your Next catch-all routes already proxy /api/* and /eve/v1/*, so nothing needed a second domain. Each pod mints its own BETTER_AUTH_SECRET and AGENT_BRIDGE_SECRET on first boot, ALLOWED_SIGN_IN starts locked to the deploying user's address rather than open, and the agent stays stopped until someone supplies AI_GATEWAY_API_KEY — a missing key removes a capability instead of throwing, per your AGENTS.md.

Two things we'd rather say up front than have you find:

  • Sign-in is Google-only, so there's a five-minute stop in the Google Cloud console after deploying — the OAuth client has to name the pod's own callback URL, which can't exist before the pod does. We show that URL and walk through it instead of letting people hit it blind.
  • We track main, not a tag, since there are no releases to pin to. If you start cutting releases we'd follow those instead.
If you want the button, this is the whole change — one line
[![Deploy on InstaPods](https://instapods.com/deploy-button.svg)](https://app.instapods.com/dashboard/pods/create?app=crm)

Reads well next to the badges under the title, or in Deploying beside the Vercel path. Tell us your referral code and we'll add it to the URL so signups are attributed to you rather than to us — that's what makes the 20% actually reach you. We're glad to open that as a separate one-line PR, or you can just paste it.

Being straight about the downside, since it's your README: it puts a vendor's name on your project, and if our page is wrong or our hosting is down, that reflects on you. Both are fair reasons to say no, and the app stays available either way — nothing here is conditional on you accepting.

No exclusivity, no licence changes, nothing asked of the code.

Contact: vikas@instapods.com — happy to move this to email or a call if that's easier than a PR thread.


Summary by cubic

Add an ADR proposing a "Deploy on InstaPods" button in the README to offer one‑click self‑hosting from source (Postgres 17, Nest API on Bun, Next app, eve agent) behind a single HTTPS hostname. It documents safe defaults (minted secrets, ALLOWED_SIGN_IN locked, agent disabled without AI_GATEWAY_API_KEY), notes Google‑only sign‑in with a brief OAuth step, tracking of main, and an optional 20% referral.

Written for commit 4a34dfc. Summary will update on new commits.

Review in cubic

@vercel

vercel Bot commented Aug 8, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the Comp AI - PoC Team on Vercel.

A member of the Team first needs to authorize it.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants