Web and application hosting for Vibe Coders
Your agent builds it. Guru Core hosts it. Hosting for coding agents to publish websites, web apps, and services. You create a workspace, then your agent can deploy, update, and run apps inside it without needing raw server access.
A simple way for an agent to get websites and apps live.
Your agent can build the site or app. Guru Core gives it a hosted workspace to publish into.
That means websites, web apps, internal tools, and services can be deployed without handing the agent your VPS or SSH keys.
You stay in control of the boundary. The agent handles the day-to-day publishing and updates inside it.
The missing piece is hosting that an agent can actually use safely.
Most coding agents can build the website or app.
The hard part is giving them somewhere to publish it without exposing your whole server.
Your agent builds fast. You deploy slow.
The app is ready quickly, then the rest of the day disappears into hosting, DNS, SSL, runtimes, and deployment steps.
Raw server access is too much power
Give an agent SSH on a mixed-purpose machine and one mistake can break config, spill across projects, or silently create drift.
Improvised setups do not last
Laptops, dev boxes, and improvised VPS setups are fine for experiments, but weak foundations for repeatable agent-led deployment.
Guru Core gives each agent a workspace where it can publish websites, apps, and services.
Create the workspace once, then hand the agent the token.
From there it can create apps, deploy files, update code, and operate safely inside that hosted environment.
Workspace-based boundaries
Each workspace has its own namespace, API token, mailbox identity, and application list, so the agent works in a bounded environment instead of on a raw server.
Real hosting primitives, not vague promises
Every app gets its own host, deploy surface, runtime shape, SSL path, and optional custom domain or IP restriction depending on plan.
Agent-first operation
The UI is there for humans, but the real model is API-first so agents can create apps, batch deploy, inspect status, and use the workspace mailbox directly.
How the agent actually uses it
The human creates the workspace in the UI, then gives the workspace API token to the agent.
The agent uses that token to create applications, deploy files, inspect status, and use the workspace mailbox through Guru Core's API.
Why this is safer than giving an agent server access
Guru Core is designed so the agent works through a bounded product surface, not raw infrastructure access.
Scoped workspace token
The agent gets a workspace bearer token, not your SSH keys and not shell access to the host.
Bounded workspace
Applications, mailbox identity, and operations stay inside one workspace boundary so projects do not sprawl across a mixed-purpose server.
Controlled operations
Provisioning, deployment, mailbox access, and application actions run through Guru Core's API and job flow instead of ad hoc server changes.
How it works
The structure is intentionally simple.
Both humans and agents should be able to understand it quickly.
Create a workspace
Sign up, create a workspace for an agent or project, and define the boundary once instead of handing over a server.
Hand the token to your agent
Your agent can then create applications, deploy files, inspect status, and use the workspace mailbox through the API.
Agent deploys. You watch.
Guru Core handles routing, SSL, logs, and access controls while your agent operates independently inside the workspace.
Frequently asked questions
Who is this for?
Solo builders, technical founders, and small teams using coding agents to ship websites, web apps, internal tools, and services.
Does the agent get server access?
No. The agent gets a workspace token and uses Guru Core's API inside that workspace boundary.
What can the agent do?
Create applications, deploy files, inspect status, manage mailbox operations, and work inside the features available on the plan.
What happens if something is still provisioning?
Guru Core uses background jobs for provisioning and apply steps, so the UI and API can show pending states honestly instead of pretending changes are instant.
Is there an uptime guarantee?
No formal uptime SLA in the MVP. Service is provided on a best-endeavours basis while the platform is still early.
Can I cancel?
Yes. Paid plans can be cancelled and the service will continue until the current billing period ends.
Start free. Upgrade when you need more capacity, control, and cleaner agent operation.
Create your account, land in the product, and get your first workspace live.
Every plan builds on the one before it, with more capacity and more control for your agent.
Free
Start with one free workspace and one application.
Create your first workspace in 120 seconds.
- 1 workspace
- 1 application
- Static and PHP apps
- 1 workspace mailbox identity
- Platform subdomain and SSL
- Basic logs
- Magic-link sign in
- Guru Core branding
Personal
For solo builders who want an agent to ship and operate small apps without babysitting the infrastructure.
- Everything in Free
- Up to 3 applications
- Hosted Node.js and Python runtimes
- Private app IP allowlists
- Restart and redeploy controls
- Remove Guru Core branding
Professional
For heavier use where the agent needs more capacity, custom domains, and room to manage multiple environments.
- Everything in Personal
- Up to 10 workspaces
- Up to 15 applications
- 1 workspace mailbox identity per workspace
- Custom domains
- Remove Guru Core branding