rivetkit

Tool passed security scan

Malicious tool definition detected

const freestyle = new FreestyleSandboxes({ apiKey: FREESTYLE_API_KEY }); const deploymentSource = prepareDirForDeploymentSync(projectDir); const { deploymentId } = await freestyle.deployWeb(deploymentSource, { envVars: { RIVET_ENDPOINT, RIVET_NAMESPACE: namespace.name, RIVET_TOKEN, }, entrypoint: "src/backend/server.ts", domains: [FREESTYLE_DOMAIN], build: false, }); // Step 4: Configure your self-hosted Rivet to run actors on the Freestyle // deployment await rivet.runnerConfigsUpsert("default"

Risky tool definition detected

Risky tool definition detected

Risky tool definition detected

--- For a production-ready single-node Rivet deployment, use the file system backend (RocksDB-based); for multi-node deployments, PostgreSQL is the recommended backend today but remains experimental as we evaluate the best fit for scalability and performance, and Enterprise teams can contact [enterprise support](https://rivet.dev/sales) about FoundationDB.

Malicious tool definition detected

Adjust the region and image as needed. ```bash gcloud run deploy rivetkit-app \ --image us-central1-docker.pkg.dev/YOUR_PROJECT/rivetkit-app/rivetkit-app:latest \ --region us-central1 \ --allow-unauthenticated \ --min-instances 1 \ --set-env-vars RIVET_ENDPOINT=<your-rivet-endpoint>,RIVET_PUBLIC_ENDPOINT=<your-rivet-public-endpoint> ``` ### Connect to Rivet 1.

Risky tool definition detected

Configure alerts to notify your team before issues become outages. ## Enterprise - **Contact [enterprise support](https://rivet.dev/sales) for production-ready deployments.** We can help with architecture review, scaling guidance, and FoundationDB support. _Source doc path: /docs/self-hosting/production-checklist_

Risky tool definition detected

**Override Configuration Path** You can override the default configuration path using the `--config` flag: ```bash # Load from a specific file rivet-engine --config /path/to/config.json # Load from a directory rivet-engine --config /etc/rivet # Load multiple paths (merged in order) rivet-engine --config /etc/rivet/base.json --config /etc/rivet/override.json ``` ## Configuration Reference ## Related - [PostgreSQL](/docs/self-hosting/postgres): Configure the experimental PostgreSQL backend - [File

Risky tool definition detected

Data Exfiltration

Privilege Escalation

Guardrail Bypass

Risky tool definition detected

You'll be provided `RIVET_ENDPOINT` and `RIVET_PUBLIC_ENDPOINT` environment variables. Create a `rivetkit-secrets.yaml` for your environment variables: ```yaml apiVersion: v1 kind: Secret metadata: name: rivetkit-secrets type: Opaque stringData: RIVET_ENDPOINT: <your-rivet-endpoint> RIVET_PUBLIC_ENDPOINT: <your-rivet-public-endpoint> ``` ### Deploy to Kubernetes

Risky tool definition detected

Enterprise teams can contact [enterprise support](https://rivet.dev/sales) about FoundationDB for the most scalable production-ready deployment. ## Basic Configuration ```json Configuration-file { "database": { "postgres": { "url": "postgresql://user:password@host:5432/database" } } } ``` ```bash Environment-variables RIVET__database__postgres__url="postgresql://user:password@host:5432/database" ``` ## Managed Postgres Compatibility Some hosted PostgreSQL platforms require additional configurati

Malicious tool definition detected

Environment=RIVET_ENDPOINT=<your-rivet-endpoint> Environment=RIVET_PUBLIC_ENDPOINT=<your-rivet-public-endpoint> [Install] WantedBy=multi-user.target ``` Replace the environment values with those from the Rivet dashboard and adjust paths to match your deployment.

Malicious tool definition detected

docker run -p 6420:6420 rivetdev/engine ``` ## Prebuilt Binaries Prebuilt binaries coming soon ## Build From Source ```bash git clone https://github.com/rivet-dev/engine.git cd rivet cargo build --release -p rivet-engine ./target/release/rivet-engine ``` _Source doc path: /docs/self-hosting/install_

Risky tool definition detected

These endpoints are accessible through the gateway at `/gateway/{actor_id}/inspector/*`. Key endpoints: - `GET /inspector/summary` - full actor snapshot (state, connections, RPCs, queue) - `GET /inspector/state` / `PATCH /inspector/state` - read/write actor state - `GET /inspector/connections` - active connections - `GET /inspector/rpcs` - available actions - `POST /inspector/action/{name}` - execute an action with `{"args": [...]}` - `GET /inspector/queue?limit=50` - queue status - `GET /inspec

Tool passed security scan

Tool passed security scan

Tool passed security scan

Tool passed security scan

Tool passed security scan

Tool passed security scan

Tool passed security scan

Tool passed security scan

Tool passed security scan