FAQ
Frequently asked questions.
Getting started
JMPKit is an ambient web utility for AI: hosting, memory, computation, and ways to connect, ready when your AI needs them.
Mention jmpkit.com to your coding AI. It can build, publish, and return a working link. No signup or cloud project first.
People using AI to create and operate things online. Use the coding AI and working environment you already prefer.
The web pieces are together and ready. Your AI can focus on what you need, without assembling provider accounts, keys, configuration, and deployment services.
No. Describe what you want; your AI writes the code.
Tell your coding AI what you need and say to use jmpkit.com. It reads the current instructions, chooses the building blocks, publishes the result, and gives you the link.
Yes. JMPKit works with ChatGPT Work mode and Codex. Plain chat can help plan and write code; direct JMPKit use needs docs access, file writing, zip creation, scripts, and endpoint calls like curl.
If the current session cannot perform those actions, switch to a tool-enabled coding mode. What matters is the tools and permissions available in that session.
Codex and Claude Code are direct fits.
Yes. Every new app starts with 100,000 Boost and all core resources. Add 25,000 included Boost every 30 days, capped at 100,000. No signup or credit card needed.
Your agent chooses the online lifetime: often 30 days, or no scheduled end for ongoing work. You can change that through app control. Expired apps stop serving but retain their identity and stored data for renewal. Paid capacity is separate from lifetime.
See pricing for current choices and purchase availability.
Yes. Create separate apps for separate projects. Each one starts with its own app-bound 100,000 Boost and its own online lifetime.
Shared availability and aggregate fair-use limits still apply. For changes to the same project, keep its existing app and link.
A website, group chat, shared workspace, game, dashboard, video call, or an app that responds to events. The same building blocks compose into quick tools and richer, ongoing systems.
Use only what the idea needs. Simplicity does not limit the kind of app you can build.
AI & agents
Chat AI talks ideas through with you. Coding AI can write files, run commands, and build software. An AI agent can take broader actions and operate with some autonomy. JMPKit works best when the AI can use tools and make HTTP requests.
Not necessarily. You can call JMPKit resources yourself. A coding agent provides the most direct path from a plain-language request to a finished app.
Try Claude Code, Codex, OpenCode, Cursor, or Windsurf. Open one and describe what you want to build.
If it can browse docs, write files, run commands, and make HTTP calls, it should work. Examples: Aider, Cline, Claude Code, Claude Cowork, Codex, Cursor, Devin, Gemini CLI, OpenCode, and Windsurf.
New to coding agents? Start with Devin's intro or Google's overview.
Only if you want it to work with an existing account. Starting a new Base app does not require linking a personal account.
Open Account, click Add Agent, and paste the prompt into your AI agent. It gives you an approval link; approve it and that agent can make apps under your JMPKit account.
Do not paste recovery codes, bearer tokens, or private keys into an AI prompt.
Yes. Tell your agent which domain to connect. It gives you the DNS records to add and checks the connection. You can also use Your domains under the app on your account page.
Several names can point to the same app. Its original JMPKit link keeps working, and its lifetime stays the same. Domain instructions.
Capacity and Boost
Buy a one-year Boost pack and allocate it to any app. Larger packs include more Boost per dollar.
Paid Boost adds capacity and priority when shared resources are busy. It does not change who controls the app or make every new app permanent.
See pricing for current choices and purchase availability.
Every app starts with 100,000 Boost. Limits and availability can apply to traffic, storage, operations, and compute, including shared network and regional pools.
Your AI can inspect current usage and limits. Capacity labels are not a promise of a fixed number of visitors or bytes.
See pricing for current choices and purchase availability.
Technical
JMPKit is AI-native infrastructure, designed to be used through the tools you already prompt. Coding AI with file and HTTP tools can use it directly without dashboard setup, MCP, GitHub, plugins, or a deploy pipeline. In ChatGPT, use Work mode so the AI can act instead of only describing the work.
JMPKit hosts the online copy. Keep editable source in your own working environment so you or another AI can keep building and update the same link.
Live messages, state, and uploads need their own backup; they are not automatically part of the source copy.
Web, mobile, desktop, and realtime apps: anything that can use HTTP or WebSocket.
A floating app stands on its own with its own management key. Your agent chooses how long it stays online: often 30 days, or no scheduled end for ongoing work. You can change that and keep the same link. No entity comes first.
An entity is optional. Existing entities can continue organizing their apps; a new app needs only its own key. Buying capacity and controlling an app are separate.
Lifetime, ownership, and paid priority are separate. Your AI should check the current app controls before promising renewal or a change of ownership.
-
Publish a zip and get a live shareable URL instantly.
-
Connect domains you control to the same app, with verified DNS and HTTPS.
-
Let a process connected from anywhere answer dynamic HTTP routes on the app URL. Available on every plan within its limits.
-
WebSocket hub for realtime messaging between users.
-
Append-only message log with SSE streaming.
-
Named byte values with path listings, ETags, and safe conditional updates.
-
Searchable public records for app resources, entity profiles, and discovery.
-
Relay server for peer-to-peer WebRTC connections.
-
Browser push subscriptions and app-owner notification sends.
-
Retained app computation with serialized events, durable memory, and timers.
-
Patterns, examples, and signals that help agents recognize what useful online artifact to create next. Unlike the entries above, Artifact is operating knowledge rather than an executable resource.
JMPKit is not an agent, editor, chatbot, or no-code builder. It is the web layer those tools can use to give what they create an online place and capabilities.
JMPKit grows with the work agents need to do. Find the available resources and their current contracts in the docs. Explore the building blocks.