Open-source client · Cross-platform · Upstream keys stay local
Fasten Share connects model-capacity producers with callers. Publish local models, private deployments, or compatible APIs you are allowed to share while the platform handles discovery, streaming routing, metering, and credit settlement.
Only connect model capacity you are authorized to use and share, and follow the upstream provider terms.
One client, two ways to participate
Producers and consumers use the same desktop client with clearly separated credentials, credits, and workflows.
Connect a model backend you are allowed to share and earn producer credits after successful consumer calls.
Find online model nodes, select a producer, and connect AI tools or API clients through one generated endpoint.
From publishing to inference
Consumers never receive a producer’s upstream key. Inference requests and responses pass through the Fasten Share service for routing, metering, and settlement.
Configure the protocol, base URL, models, and locally stored credential in the client.
The producer opens an outbound connection and runs health checks so unhealthy backends leave discovery.
A consumer finds a node and sends standard HTTP or streaming requests to the generated Fasten Share endpoint.
The service meters actual forwarded usage and tracks consumer and producer credits separately.
Works with your existing setup
Exact compatibility depends on the protocol and tool capabilities published by each producer. The current client UI is authoritative.
Core capabilities
Consumers call the endpoint generated by Fasten Share without receiving a producer’s original upstream credential.
Connect Ollama, LM Studio, vLLM, and OpenAI-, Anthropic-, or Azure OpenAI-style APIs.
Periodic checks reduce the exposure of nodes with authentication failures, exhausted quota, or unavailable endpoints.
Search by model and protocol, then use availability, follows, and recent three-month ratings to choose a producer.
The platform forwards requests and responses between consumer HTTP and the producer’s outbound connection, including streaming content.
Actual forwarded data is metered centrally while consumer and producer credits remain separate.
Security boundary
A producer’s upstream API key is stored by the local client and injected only when it calls the model backend. It is not sent to consumers or the Fasten Share service. Consumer prompts and model responses do pass through the service to enable routing, metering, and settlement, so always use the official HTTPS domain.
Inspect the client on GitHub →The producer client is MIT-licensed, including the local credential and request-forwarding implementation.
Adjust concurrency and the credit multiplier, stop an individual backend, or take the client offline at any time.
Do not connect capacity you may not forward or that violates upstream account, subscription, or commercial-use terms.
Start with a concrete problem
Step-by-step help for local models, compatible APIs, CLIProxyAPI, and AI tool configuration.
From authorization and backend preparation to health checks and producer credits, learn how to share idle model capacity without ignoring credential, policy, or income risks.
Read guide →Learn how Fasten Share connects model-capacity producers and consumers through discovery, streaming routing, credential separation, usage metering, and credit settlement.
Read guide →Configure Ollama connectivity, model IDs, an OpenAI-compatible endpoint, Fasten Share health checks, and resource limits to share a local model responsibly.
Read guide →No. The upstream credential stays on the producer device and is injected by the local client when it calls the backend. Consumers and the Fasten Share service do not receive it.
Yes. The service performs discovery, routing, authoritative metering, and credit settlement, so prompts and responses are forwarded through the official HTTPS service.
You can connect local models, private deployments, or compatible online APIs you are authorized to share. Exact protocols and models depend on current client support and your configuration.
No. Producer credits come from successful usage. Withdrawal eligibility, exchange rates, thresholds, review, and payout rules are those shown in the client when you apply; no fixed income is promised.
Sign in, create a consumer API key, find and select a model node, then copy its generated endpoint or use the tool configuration assistant.
Desktop packages are published for Windows, macOS, and Linux. Check the download page for currently available builds and versions.
Use one Fasten Share client for producer setup, node discovery, and AI tool configuration.
