Forms and app records
Store structured submissions, preferences, orders, or application records in named collections.
A factual guide to kkbase capabilities, limits, suitable use cases, and excluded infrastructure services.
Each capability below is exposed through the customer portal or authenticated data API.
Create and manage separate kkbase projects from one customer account.
Generate or revoke project keys with database read and write permissions.
Create, list, update, and delete JSON records in named collections.
Upload CSV or JSON records into a collection without a support ticket.
Protect JSON API records automatically each day and restore a completed backup through the portal at no additional charge.
Deploy a ZIP web app on kkbase or host the frontend elsewhere while using the authenticated data and local AI APIs.
Call the plan-configured local model through a project key without exposing Ollama directly.
Browse records, review plans, and track billing or technical questions.
kkbase suits applications that need a straightforward authenticated JSON record layer.
Store structured submissions, preferences, orders, or application records in named collections.
Use scoped keys to connect an internal dashboard or workflow to a shared record API.
Begin with the Free plan, validate the workflow, and move plans when request volume grows.
These boundaries keep the service description accurate and help customers choose appropriately.
CSV and JSON imports are transactional. A failed batch adds no records.
Backups are not full PostgreSQL images and do not provide point-in-time recovery.
Actual response time depends on the customer’s location, network, and application.
A direct comparison of the customer-facing service and infrastructure that is not currently sold.
Availability still depends on an active account and the selected plan’s published limits.
Start on Free, generate a scoped API key, and use the API or self-service importer from your portal.