Provider gateway
Route models, credits, tasks, and results through one control layer.
Core capabilities
The systems behind a repeatable AI SaaS business.
ZShip combines model delivery, first-use conversion, customer accounts, and post-purchase operations in one Cloudflare-native platform.
Guest activation
Let visitors reach a useful first result before asking for an account.
Image Agent
Generate and edit images through a durable conversation workspace.
Customer delivery
Connect checkout, licensing, downloads, support, and content.
Provider gateway
One control layer for external AI models.
Connect KIE, WaveSpeed, Replicate, and other providers through a common task, credit, routing, and storage model. Projects can expose selected models without embedding provider-specific logic in every frontend.
01
Product request
An app sends model intent, inputs, and project context.
02
Provider gateway
Routing, credits, validation, limits, moderation, and callbacks run at one boundary.
03
Durable result
The task and generated asset return through a stable product-facing contract.
Configuration over rewrites
Manage providers, models, field mappings, defaults, credit costs, and plan allowlists from Admin.
Usage and credit control
Tie model usage to credits, subscriptions, app_key scope, and auditable task records.
Safety at the gateway
Apply rate limits, API key controls, content moderation, and failure policies before upstream calls.
Async operations
Normalize callbacks, retries, file transfer, task logs, and public gallery flows.
Conversion path
Let users experience value before asking for commitment.
The first-use path connects public demos, guest access, free credits, account creation, payment, and ongoing usage in one product flow.
Guest access
Let visitors try the product without creating an account when the project enables guest access.
Welcome credits
Grant an initial credit balance so the first session can reach a meaningful result.
Account conversion
Move a useful first session toward a registered account and a durable customer workspace.
Reasons to return
Use check-in, credits, subscriptions, content, and support to continue the relationship.
Guest access and free-credit limits are configured per project, with application checks and database rules enforcing the configured boundary.
Image Agent
A conversational workspace for generating and editing images.
Image Agent keeps the conversation, task run, references, and image versions together so users can continue from the work they already started.
Conversation to asset
A single workspace for prompts, references, generation, editing, and review.
Describe
Explain the image or edit in natural language.
Guide
Attach or import references and continue from prior results.
Keep
Store durable results on the product CDN with credit tracking.
Multi-turn editing
Continue an image conversation instead of starting a separate generation form for every change.
Resumable task state
Keep the run, image versions, and library state available after a refresh.
Isolated usage billing
Connect provider work to the user's project and credit ledger.
Customer platform
The product continues after checkout.
ZShip treats delivery and customer operations as part of the product surface, so buyers can find the next step without leaving the platform.
Checkout and billing
Backend-driven plans, payment status, subscriptions, credits, and purchase history.
Licensing and delivery
Orders, licenses, GitHub access, downloads, and delivery status in one account.
Support and recovery
Tickets, account sessions, access recovery, and customer-facing status messages.
Content and store
Docs, blog, changelog, roadmap, showcase, components, and credits-linked purchases.
Cloudflare-native foundation
Separate services, one customer experience.
The public product uses independent services behind a shared tenant and delivery model.
Service boundaries
Auth, billing, AI, support, storage, content, and delivery can evolve independently.
app_key scope
One foundation can support multiple products while keeping data and operations scoped.
Edge deployment
Nuxt, Astro, Pages, Workers, D1, KV, and R2 form the default deployment stack.
Service bindings
Internal calls stay on the Cloudflare network while public APIs remain explicit.
See it in context
Start with the platform surface your customers actually use.
Review the pricing flow, read the implementation docs, or explore products built on the platform.