Technical documentation

RuntimeForce FAQ

Clear answers about installation, architecture, project isolation, model providers, data handling and billing.

1. What is RuntimeForce?

RuntimeForce is a local-first AI development environment. The IDE runs on your computer and combines project files, editor, terminal, Git workflows, AI agent modes, local model runtimes and remote SSH workspaces. The hosted service provides account authentication, subscriptions, billing and plan entitlements.

2. Does the RuntimeForce server store my source code or project files?

No. The hosted RuntimeForce service is not a remote code workspace. Project files, local workspace contents, prompts, chat history and local memory remain in the local IDE environment. For cloud inference, the selected prompt and context are sent directly from the IDE to the AI provider you configure. Review the Security documentation for the complete data-flow description.

3. Is the entire SQLite database encrypted?

No. RuntimeForce does not currently encrypt the SQLite database file as a whole. Supported credential fields are encrypted with AES-256-GCM using a local master key. The master key is stored in the local IDE environment configuration. Use operating-system account protection and full-disk encryption to protect the database and local configuration at rest.

4. Does every project have its own Workspace and SSH configuration?

Yes. Workspace records are associated with a project. Each project can use its own local folder or SSH connection. Creating a project does not attach the last active workspace or SSH host; configure the connection in that project's settings.

5. Can I connect a different GitHub repository to each project?

Yes. Repository remote URL, main and development branch preferences, Git mode and versioning settings are stored on the project record. Git status, diff, commit, push and pull operations are scoped to the selected project's workspace. GitHub account authorization is used to access repositories you are permitted to use.

6. Which AI providers can I use?

RuntimeForce supports local model runtimes such as Ollama and LM Studio, plus supported cloud providers configured with your own API keys. The exact provider list is subject to current integration support and the features enabled for your plan. Provider pricing, free quotas, rate limits and data policies are controlled by each provider.

7. Can I work without an internet connection?

A local model runtime does not need an internet connection once the model is installed. Cloud AI providers require connectivity. RuntimeForce account verification and plan-entitlement refreshes use the hosted service, so do not assume the entire IDE or every protected feature is available offline. The offline-grace value shown on a plan is controlled by its entitlement settings; check the current release notes before relying on it for a disconnected production workflow.

8. What are the system requirements for local models?

The IDE supports Python 3.11+ and Git on Linux, macOS and Windows. Local model requirements depend on the model size, quantization, available RAM / VRAM and your CPU / GPU. Ollama or LM Studio must be installed separately if you want local inference. Cloud BYOK can be used when local hardware is insufficient.

9. How does billing work with BYOK?

With BYOK, you supply the provider API key and the provider bills you under its own pricing and quota rules. RuntimeForce subscription fees cover the RuntimeForce plan features and limits, not the provider's API usage. Local model inference does not incur provider API charges.

10. Are trials, cancellations and refunds available?

Trial availability and duration are shown on the relevant plan at checkout. You can manage or cancel an active subscription from your account. Creem processes payments as Merchant of Record. Refund eligibility is governed by the terms shown at checkout and applicable consumer law; contact support if you need help with a billing issue.

11. What is ATM?

ATM means Automated Team Mode. It coordinates specialist agent roles across a multi-step task. Availability depends on the features enabled for your current plan.