platform / security

Decide who gets in.Know what you ship.

Choose who can reach each service, from your own team to your identity provider, and check every build for vulnerable packages before it goes live. One checklist shows where every service stands.

Run your apps securely

Built in Czechia, hosted in the EU · No credit card required

Checklist

See which services need attention.

One checklist per service shows what is set up and links straight to what is missing.

Security in Rock8Cloud covers two areas.

Security checklist
The Security checklist with 6 of 6 passing: access set to org members, dependency scan on every build, deploys blocked at Critical, daily background scans, the latest scan passed, and one channel receiving security alerts
01Access

Only the right people can open your app.

Pick who gets in. Previews follow the same rule, and nothing is redeployed.

Every plan

Not exposed

No public URL. Only your other services reach it.

Every plan

Anyone with the link

Public. No sign-in.

Every plan

Members of this organization

Your team signs in with Rock8Cloud. Nobody else gets in.

Earth+

Password

One username and password before the app loads.

Earth+

OIDC provider

Sign in with Okta, Entra ID, Google Workspace or Keycloak.

Members of this organization · every plan

Make your app visible only to your team.

The easiest way to keep an app private. Nobody shares a password and there is no identity provider to set up. Remove someone from your organization and they lose access within an hour. Included in every plan.

01

Invite your team

Add people to your Rock8Cloud organization by email.

Settings · Members
The Invite Member dialog in organization settings with jonas@rock8.cloud entered and the Member role selected
02

Choose Members of this organization

One click on the Security tab. It covers every preview and custom domain.

Security · Access
Who can reach this service with Members of this organization selected, and the path from visitor through Rock8Cloud sign-in to the service
03

Only your team gets in

Members sign in with their Rock8Cloud account. Everyone else is turned away.

Your team
The private site sign-in for customer-portal.rock8cloud.app: Sign in to continue, only members of the organization that owns this site can open it, Continue with GitHub
Everyone else
The No access to this site page for customer-portal.rock8cloud.app shown to someone outside the organization, with a button to sign in with another account

Your app is never left open by mistake.

See at a glance that every environment is protected. If protection ever fails, your app is taken off the internet instead of staying open to anyone.

Environments
The Environments panel: Main at customer-portal.rock8cloud.app and the previews for PR #142 and PR #147 each marked Protected

Use the login your company already has.

Connect your identity provider in three steps.

  1. 01

    Choose your provider

    Okta, Microsoft Entra ID, Google Workspace, Keycloak or any OIDC issuer.

  2. 02

    Register the URLs

    Copy the callback URLs we list for Main and each preview.

  3. 03

    Save

    Optionally block cross-site writes with CSRF protection.

Security · Access · OIDC
OIDC setup for the admin-console service: Okta chosen as the identity provider, the callback and post-logout URLs of Main and the PR #58 preview with copy buttons, and CSRF protection switched on
02Code security

Stop known vulnerabilities before they reach production.

New vulnerabilities (CVEs) in open-source packages are published every day. We check the packages your app uses and tell you which version fixes each one.

  1. 01Can block

    On every build

    Risky builds are stopped before they go live.

  2. 02Reports only

    On a schedule

    Catches new CVEs in the code that is already running.

  3. 03Reports only

    On demand

    Scan any time with one click.

Security · Vulnerabilities
Open findings of the customer-portal service: the latest scan passed with 0 critical, 2 high, 3 medium and 2 low findings, listed with CVE ids, the axios, micromatch, request and tar packages, installed and fixed versions, and the Fix with agent and Scan now buttons
Every finding with the version that fixes it

See exactly what blocked a deploy

Every finding, with the version that fixes it.

Deployment · Vulnerabilities
A failed deployment, Add PDF export to invoices, blocked by its build scan: 1 critical finding, CVE-2025-29927 in next 14.1.0, fixed in 14.2.25, plus high, medium and low findings
Background scans · every plan

Know when a new vulnerability hits an app you already shipped.

Vulnerabilities are often found months after an app goes live. Background scans re-check the apps you already run and tell you when something new turns up, without touching the deploy.

  1. You shipBuild scan passes
  2. Daily scanAll clear
  3. Daily scanAll clear
  4. New CVE foundIn a package you run
  5. You get an alertSlack, Discord or webhook
  6. Fix with agentUpgrades in a pull request

Your schedule

Hourly, daily, weekly or monthly, in your time zone.

Only what matters

Get pinged on Slack, Discord or a webhook from the severity you choose.

A weekly digest

Every Monday, one summary of open findings per project.

Background scans
Background scans set to Daily at 09:17 in Europe/Prague, with the next three runs listed
Notifications
Notifications set to Medium and above, the service included in the weekly digest, and the #security-alerts Slack channel receiving new vulnerabilities and the weekly digest
Scan history
Scan history of customer-portal: scheduled, manual and build scans over two weeks, with a scheduled scan and a build scan failing on 1 critical finding and every scan after the upgrade passing

See every scan and what it found

Result, trigger, commit and new findings for each scan, kept for 90 days by default.

  • Build
  • Scheduled
  • Manual
Fix with agent

Let an agent fix it for you.

An agent upgrades the packages, runs your tests and opens a pull request.

  • Upgrades each package to its fixed version
  • Runs your tests and build
  • Opens a pull request with what it fixed
Agent session
An agent session started with Fix with agent: the prompt lists the findings, and the agent reports it upgraded axios, micromatch and tar, left request open because it has no fix, and opened pull request #151
MCP

Secure your apps from your AI chat.

Claude, ChatGPT, Cursor or any MCP client can lock services and run scans for you.

Lock a staging site

Puts a password in front of the service and hands you the login.

“Put docs-staging behind a password and give me the login”

Take a worker offline

Removes the public URL. Services in the same project still reach it.

“Take billing-worker off the internet”

Check before a release

Scans the commit that is running now and reports what it found.

“Scan customer-portal and list anything high or critical”

Fix what it found

Reads the findings and opens a pull request with the upgrades.

“Upgrade the vulnerable packages in customer-portal and open a PR”

Agent tools: set_service_access, scan_service, list_vulnerabilities

Previews included

One choice covers Main and every preview.

Never left open

If protection fails, your app goes offline instead of public.

Your threshold

Block deploys at Critical, at High and above, or only report.

Alerts where you work

New findings go to Slack, Discord or a webhook, plus a weekly digest.

Fix with agent

An agent upgrades the packages, runs your tests and opens a pull request.

A checklist per service

Six checks per service, each linking to the fix.

Security FAQ

Questions beforeyou lock it down.

Plans, what gets scanned, and what changes when you save.

Dependency scanning, Members of this organization, Not exposed and Anyone with the link are on every plan. Password and OIDC protection need the Earth plan or higher. Fix with agent runs a regular agent session and is metered like one.

The JavaScript lockfiles in the build context: package-lock.json, pnpm-lock.yaml, yarn.lock and bun.lock. It reports findings of every severity with the fixed version where one exists. A repository without a supported lockfile is skipped, and nothing is blocked.

No. Saving never starts a build or a deployment. Running environments update in place, and the Environments panel shows each one move to Protected.

No. Access protection is a gate in front of the whole service, not a sign-in system for your app. If your app needs to know who the user is, give it its own sign-in.

Members of this organization and Password cover the service URL and every verified custom domain. OIDC protects the service URL of each environment and cannot be combined with custom domains.

No. Scheduled and manual scans only report. Only a build scan can stop a deploy, and only for findings at or above the threshold you set.

Ship today

From idea to productionin one prompt.

  • No repo yetMCP

    Prototype this idea from a blueprint

    Rock8Cloud forks a ready-made stack into your GitHub and deploys it.

  • Have a prototypeMCP

    Get my prototype live

    Rock8Cloud builds it, wires the database and env vars, and puts it live.

30 days free. No credit card required to start.