Skip to content

blog: Introducing Rivet BYOC - #65

Merged
NicholasKissel merged 1 commit into
mainfrom
NicholasKissel/introducing-rivet-byoc
Sep 15, 2026
Merged

NicholasKissel merged 1 commit into
mainfrom
NicholasKissel/introducing-rivet-byoc

Conversation

@NicholasKissel

Copy link
Copy Markdown
Member

Adds the Rivet BYOC changelog post for 2026-09-15.

  • src/content/posts/2026-09-15-introducing-rivet-byoc/page.mdx: post covering the operator model, BYOC for your own customers, and the 14-day trial. Hero is uploaded to R2 at website/blog/2026-09-15-introducing-rivet-byoc/image.png; the frontmatter references image.png?v=2 to bypass a stale Cloudflare edge cache of the first upload.
  • create-launch-post skill: the tile renderer referenced the purged Perfectly Nineties font and now uses Manrope; adds --ink-tile (Rivet product-mark badge, sized level with neighboring tiles), --no-wordmark, and a viewBox fallback for SVGs that only declare width/height.

Verified locally: post renders at /changelog/2026-09-15-introducing-rivet-byoc/, all internal links return 200, renderer scripts type-check.

Adds the Rivet BYOC changelog post for 2026-09-15 and updates the
create-launch-post tile renderer: Manrope replaces the purged Perfectly
Nineties font, adds --ink-tile (Rivet product-mark badge sized level with
its neighbors), --no-wordmark, and a viewBox fallback for SVGs that only
declare width/height.

Amp-Thread-ID: https://ampcode.com/threads/T-01a0a1ba-571f-72d8-a85e-924a49ba90b7
Co-authored-by: Nicholas Kissel <nicholas@rivet.gg>
@railway-app
railway-app Bot temporarily deployed to rivet-website / website-pr-65 September 15, 2026 03:31 Destroyed

@the-company-company the-company-company Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟠 1 medium · 🔵 1 low

Reviewed commit 3f8a50e.


Today we're releasing **Rivet BYOC** (Bring Your Own Cloud): the Rivet control plane deployed inside your own AWS or Google Cloud VPC and managed by Rivet.

Until now you had two options. Rivet Cloud runs everything for you, or you self-host the control plane and own the provisioning, upgrades, and on-call that come with it. BYOC sits between them. Your data and compute stay in your account. Rivet handles deployment, updates, and maintenance.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟠 Medium · Replace the prohibited compute deployment term

compute is explicitly reserved for the live Rivet Compute feature and is prohibited as a name for a process running a customer's code. Here it makes the BYOC data-residency claim ambiguous with that separate product. Refer to the customer's backend (or workers where appropriate) instead.

Comment on lines +36 to +38
## Links

- [BYOC docs](/cloud/byoc)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔵 Low · Include the required source repository link

The launch-post format requires the final links section to include the relevant GitHub repository alongside docs and Discord. This list omits it, leaving readers without the prescribed source/issue-tracking destination. Add the BYOC/Rivet repository link here.

@NicholasKissel
NicholasKissel merged commit 59020f7 into main Sep 15, 2026
4 checks passed
@NicholasKissel
NicholasKissel deleted the NicholasKissel/introducing-rivet-byoc branch September 15, 2026 03:34
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