Deploy Tealbrick Marketplace — source v0.1.7

Governed agent integrations, built from public source on Railway.

Deploy Tealbrick Marketplace — source v0.1.7

Just deployed

/data

Deploy and Host Tealbrick Marketplace

Build Marketplace v0.1.7 from its public source inside your own Railway project. The protected release-marketplace-v0.1.7 branch resolves to a031f6ecb709c74900c1b3344dba9c48c488a9b4. No Tealbrick GHCR credentials are required. The repository license governs use; public source is not a license purchase.

About Hosting

One service listens on port 5314 with one persistent /data volume. The tracked entrypoint prepares private state directories as root and then runs as uid 1000. Do not override the entrypoint. Instance-specific secrets are generated for each install; preserve the handoff encryption key across restart, upgrade and restore. Protect database and provider-settings backups separately from that key.

Why Deploy

Keep integration configuration, provider credentials and application state in your Railway project. Marketplace applies explicit tenant and agent authorization rather than trusting browser-supplied labels. Deployment alone does not grant an agent access.

Common Use Cases

Configure integrations for agents through a trusted Tealbrick Portal, then authorize exact capabilities and provider accounts. Use a separately consented read-only provider canary before enabling consequential operations.

Dependencies for Tealbrick Marketplace

Supply the exact Portal-issued deployment, organization and workspace identifiers, your operator identity, and an authorized Rules endpoint and tenant-scoped evaluation-only credential. Do not invent identifiers or substitute an administrator credential. If you do not yet have these, finish Portal provisioning first.

Deployment Dependencies

Public source: https://github.com/Tealbrick/marketplace/tree/release-marketplace-v0.1.7 . Build root: release/railway. Health: /healthz is liveness only. Protected /api/portal/readiness validates Portal and Rules bindings; a healthy Railway service is not proof that provider OAuth or agent grants are complete. Provider accounts and keys are configured separately in the trusted runtime. Never paste service keys into a chat or public source. Full contract: https://github.com/Tealbrick/marketplace/blob/dc3d929351552b88e00de77e1c618a3f0960ab7a/deploy/railway/RAILWAY.md .


Template Content

More templates in this category

View Template
N8N Main + Worker
Deploy and Host N8N with Inactive worker.

jakemerson
121
View Template
Evolution API with n8n
Automate WhatsApp workflows with Evolution API, n8n, and Postgres.

codestorm
96
View Template
Postgres Backup
Cron-based PostgreSQL backup to bucket storage

Railway Templates
870