Question 1

What is it?

Accepted Answer

cohesivity’s primary public hosting path, running on Railway. cohesivity owns the Railway project, service, environment, and provider credentials, so your agent only ever talks to cohesivity.

Question 2

What can I build with it?

Accepted Answer

One public web app or site that runs as a single Railway web service. V1 is hosting-only: one service, one production environment, one Railway-provided service domain, plus the vanity and custom domains cohesivity manages for you.

Question 3

How does it get set up?

Accepted Answer

Your agent provisions railway-hosting, uploads the files straight through cohesivity, and waits for a stable Railway deployment state. It gets back one cohesivity.app deployment URL that uses shared edge TLS immediately, while the edge forwards to Railway’s generated HTTPS origin. Railway service and dashboard URLs stay internal. If the wait times out, the reply says pending rather than pretending the app is ready. There is no GitHub source connection, Railway CLI, tenant Railway account, or Railway dashboard step.

Question 4

What can my agent manage?

Accepted Answer

The whole v1 hosting loop over the cohesivity API: deploy by upload, list deployments, read deployment details, fetch build, runtime, and http logs, manage environment variables, claim a cohesivity.app vanity host, attach BYOD or cohesivity-purchased domains, and read domain and status details.

Question 5

What does my agent call?

Accepted Answer

Five HTTP calls cover the loop. POST /api/resources/railway-hosting creates the managed service, once, before the first deploy. POST /api/railway/deploy?wait=ready uploads the source files and waits through a short success-stability window; a timeout comes back pending, so your agent can poll instead of announcing a deploy that has not settled. GET /api/railway/domain returns the public cohesivity.app route. POST /api/railway/custom-subdomain claims a *.cohesivity.app vanity host with the same shared edge certificate, so there is no per-host certificate wait. POST /api/railway/domains attaches a domain you already own or bought through cohesivity, using cohesivity-owned Railway auth.

Question 6

How is it capped?

Accepted Answer

cohesivity sets tier compute caps on Railway and reconciles them when an ephemeral tenant is claimed or the resource is provisioned again. Topology, replicas, and scaling controls are not something a tenant requests; every tier keeps one replica.

Row	tier	cpu	ram	replicas	sleep
1	Ephemeral + claimed Free	0.5 vCPU	1 GB	1	on
2	Plus	1 vCPU	2 GB	1	off
3	Pro	2 vCPU	4 GB	1	off

Hosting

What you get, by default.

Direct upload

Domains, managed

Endpoints

Fixed compute caps for v1.

Ephemeral + claimed Free

Plus

Pro

Questions.