# FAQ

> Common questions about how Ownkube works, what it costs, and what you get.

## General

<details>
<summary>What is Ownkube?</summary>

A cloud for personal software. Push a repo or a container and Ownkube builds, deploys, and runs it, with a live URL, managed Postgres, automatic TLS, logs, metrics, autoscaling, and rollbacks built in. No cloud account, no cluster to provision, no platform team. When you want your own data boundary, the same app runs in your own AWS account with the same workflow and dashboard.

</details>

<details>
<summary>Do I need a cloud account?</summary>

No. Ownkube runs your apps on infrastructure it owns and operates, and you pay Ownkube for what you use. Connecting your own AWS account is an option for when you want your own data boundary or your own bill, not a requirement.

</details>

<details>
<summary>How is this different from Heroku, Render, or Railway?</summary>

For managed compute it is the same kind of workflow: push code, get a live URL, no servers to manage. Ownkube is metered per minute (about a third under the equivalent Railway bill) with managed Postgres and autoscaling built in. What those platforms don't offer is the option to run the **same app** in your own AWS account when you need it, with no rewrite and the same dashboard and observability.

</details>

<details>
<summary>Can I use Ownkube without a credit card?</summary>

You can sign in and look around without a card. To deploy on Ownkube-hosted compute, top up the wallet from \$5 with no subscription, or pick a plan from \$5/month. Running in your own AWS account is an Advanced path with its own no-card option; see [Clusters](/docs/features/clusters).

</details>

## Deployments

<details>
<summary>What kinds of workloads can I run?</summary>

**Web apps** (HTTP services), **workers** (long-running background processes), **jobs** (one-off or cron), **databases** (managed PostgreSQL), and **[Functions](/docs/features/functions)** (beta, serverless event handlers triggered by HTTP or a cron schedule). See [Deployments](/docs/features/deployments).

</details>

<details>
<summary>What frameworks and languages are supported?</summary>

Anything that runs in a container. Build from a GitHub or GitLab repo (with or without a Dockerfile), or push an image to a connected registry. Node, Python, Go, Ruby, Rust, Java are all supported.

</details>

<details>
<summary>Are public hostnames and TLS automatic?</summary>

Yes. Toggle **Make this deployment public** on the deployment **Settings** tab and Ownkube assigns a generated `*.ownkube.app` hostname with an automatically provisioned and renewed TLS certificate. See [Deployments](/docs/features/deployments).

</details>

<details>
<summary>Can I run cron jobs?</summary>

Yes. Create a **Job** deployment and add a schedule (standard cron syntax). See [Deployments](/docs/features/deployments#job).

</details>

<details>
<summary>How do I deploy updates?</summary>

Push a new commit (for source deployments) or a new image tag, and Ownkube rolls new containers out and drains the old ones after health checks pass. A bad rollout is a one-click rollback to the last healthy revision.

</details>

## Billing and costs

<details>
<summary>What am I paying Ownkube for?</summary>

On Ownkube-hosted compute, a prepaid wallet: top up as you go from \$5 with no subscription, or pick Personal at \$5/month or Team at \$20/month, metered per minute at about \$0.00041/vCPU-minute and \$0.0001/GiB-minute for what your apps actually use. A mostly-idle app costs very little. See [Pricing](/docs/configuration/pricing).

</details>

<details>
<summary>Do I need a plan to start?</summary>

No. Pay as you go has no subscription: top up the wallet from \$5 and deploy. A plan (Personal at \$5/month or Team at \$20/month) loads credit each month and unlocks more. Running in your own AWS account has its own no-cost option on the Advanced path; see [Clusters](/docs/features/clusters).

</details>

<details>
<summary>Can I cap my monthly spend?</summary>

Yes. Set a **monthly budget** and choose to be notified at the cap or to have your apps **pause** (scale to zero, data retained) when month-to-date spend reaches it. Spending alerts email the account owner at 50%, 80%, and 100% of the budget. See [Spend limits](/docs/configuration/pricing#spend-limits).

</details>

<details>
<summary>Is there an Enterprise plan?</summary>

Yes, with custom pricing, volume discounts, SLAs, SSO, and advanced access controls. [Contact us](mailto:support@ownkube.io?subject=Enterprise). Enterprise is not self-serve.

</details>

## Running in your own cloud

Everything above describes Ownkube Compute, the default, no cloud account needed. When you want your own data boundary or your own AWS bill, the same app runs inside your own AWS account instead, with the same workflow and dashboard. That's the Advanced path, covered on its own pages:

- [Clusters](/docs/features/clusters)
- [Connect AWS](/docs/guides/connect-aws)
- [Security](/docs/configuration/security)

## Security and compliance

<details>
<summary>Does Ownkube see my application data?</summary>

On Ownkube-hosted compute, your apps run in isolated, encrypted infrastructure Ownkube operates. See [Security](/docs/configuration/security) for the data boundary on the own-cloud path.

</details>

<details>
<summary>What IAM permissions does Ownkube need in my account?</summary>

For the own-cloud path, a scoped, least-privilege role, not admin access. See [Connect AWS](/docs/guides/connect-aws#what-the-iam-role-can-do) for the exact permissions.

</details>

<details>
<summary>Is my data encrypted?</summary>

Yes. At rest and in transit with TLS on every hop. Secret env vars are encrypted before delivery to the runtime secret store, which is itself encrypted at rest.

</details>

<details>
<summary>Can I meet SOC 2 / HIPAA / GDPR requirements?</summary>

Compliance posture depends on which path you run on. See [Security](/docs/configuration/security#compliance-posture) for details.

</details>

## Teams and access

<details>
<summary>How do I invite teammates?</summary>

Open [Settings](https://app.ownkube.io/dashboard/settings), go to the **Organization** section, and invite by email. See plan limits for seat count on your tier.

</details>

<details>
<summary>Is there SSO?</summary>

SSO is part of the Enterprise plan. [Contact us](mailto:support@ownkube.io?subject=SSO).

</details>

- [Pricing](/docs/configuration/pricing)
- [Security](/docs/configuration/security)

---

**Don't see a feature you need?** Email [support@ownkube.io](mailto:support@ownkube.io?subject=Feature%20request). Ownkube is shaped by the teams using it and we ship what our users ask for.
