You choose the endpoint
Connect a self-hosted model service, compatible gateway, or internal API instead of hard-coding one provider into the client.
When code cannot casually enter a third-party SaaS, Cocode provides a client entry point for self-hosted endpoints, private gateways, and controlled workspaces.
Capabilities and limits follow the current release
Connect a self-hosted model service, compatible gateway, or internal API instead of hard-coding one provider into the client.
Files, commands, network actions, and model requests have visible boundaries that are easier to review in a team environment.
A private endpoint does not mean falling back to scripts. GUI, TUI, sessions, diffs, and tests remain one workflow.
Cocode treats self-hosting as an engineering boundary: know where files live, where requests go, which actions need confirmation, and how results are recorded.
Clear boundaries make real development work easier to trust.
Choose an internal service, private gateway, or compatible API based on security and cost requirements. The client connects it to the same task context.

A developer can review task context, files, and diffs in the GUI, then continue execution from a controlled server through TUI or SSH.

No. Cocode is the client and workflow layer. It supports self-hosted model endpoints and private gateways; whether the model service is self-hosted depends on your deployment.
It fits developers, platform teams, and engineering organizations that need control over code boundaries, model request paths, network permissions, and task context.
If the model endpoint matches the protocol and capabilities supported by the current client, a local or internal model can be used as the entry point.