xpod

Put the AI runtime inside your own boundary

xpod provides pods, identity, storage, permissions, and agent runtime so the system can run closer to your own data instead of being forced back into a remote platform.

See deployment guide Support development

Local-firstSelf-hostableIdentity and permissionsAI APIs

xpod Runtime

identity / secrets / contained runtime

contained runtime healthy

CSS healthyAPI healthy

ganlu.xpod.aipolicy live

CSS service running

API service running

Base URL ganlu.xpod.ai

Overall healthy

Boundary Surface

Pods / WebIDs / Keys

Identity, Pods, and developer keys stay here so runtime requests land on a clear boundary surface.

https://pod.ganlu.me/

Pod

pod

https://id.ganlu.me/profile/card#me

WebID

webid

runtime-admin

API Key

scoped

render_api_token / SIT

Request

approval

Service Monitor

Logs and runtime state

xpod does not just hold secrets. It also holds service state, restart control, and logs on the same boundary surface.

deploy: localtunnel: cloudflaremode: direct

08:14 warn api

pending approval queue depth=2

08:15 info api

credential rotation check completed

08:16 info css

solid server bound to 0.0.0.0:3000

What xpod does

If LinX is where you start using the system, xpod is the layer that keeps it running, keeps context with you, and lets many agents work inside a boundary you control.

Always on

Your AI Secretary Never Stops

Runs 24/7, even when you are not talking to it. It can stay on tasks, watch progress, and keep work moving.

Context

All Your Pieces, In One Place

Data, memory, and working context come back into one system, with identity, permissions, and portable interfaces you control.

Boundary

One Secretary, Many Agents

One aligned layer can direct many agents while keeping privacy and control inside your boundary.

Hosted preview and support path

xpod Cloud currently stays a hosted preview with a free baseline instead of a formal subscription. Support goes through a separate donation path, and supporter status is claimed manually rather than turned into a bigger resource tier.

Current

Free baseline

The hosted preview starts from platform-controlled default quotas instead of a billing plan.

Support

Support development

Donations support development, infrastructure, and operating costs. They do not automatically raise storage, bandwidth, or model quotas.

Principle

Self-hosting first

If you need stronger guarantees and more control, xpod still prefers self-hosting over locking the product behind a managed subscription first.

When you need it

Look at xpod when deployment location, permission control, and keeping data in your own environment become first-order concerns.

Run AI on your own device or server
Keep AI close to data you already control
Avoid turning identity and permissions into a platform black box

How it fits the stack

LinX handles the product surface, xpod handles the runtime, and drizzle-solid keeps connecting more data and workflows.

Next step

Start with the runtime

If your first question is about deployment and control, start with xpod.

See docs Support development Back home