Support, security and lifecycle
Use the channel that matches the problem. Support runs through the public channels below; response-time and uptime commitments come only with a separate written agreement.Get help or report a problem
Never post keys, cookies, provider URLs or credentials, billing details or
personal data in an issue. If a report needs sensitive evidence, open a
redacted issue and ask for a private channel.
For Cloud status, check the
public status page and
/api/health. If your workload can’t tolerate
an outage, keep a previous endpoint or a self-hosted deployment as a rollback.
Report a security vulnerability
Emailjaxernst@gmail.com; don’t open a public issue. This is the same channel
as the RPC Core security policy.
Include enough detail to reproduce the problem, but no live production
credentials. Confirmed issues are fixed and disclosed on a timeline agreed with
the reporter.
To harden a self-hosted deployment, see the Core
security considerations
and the production checklist.
Versions and lifecycle
RPC Core fixes land in the latest published release; upgrade older versions before requesting a fix. In production, run a versioned GitHub release by its recorded container digest, and read each release’s compatibility notes before upgrading, since Core is pre-1.0. See versions and evidence. Lasso Cloud deploys continuously; What’s new lists each production release. Build automation against the liveopenapi.json and
agent.json, which report what the deployed
service serves.