Questions
The ones people actually ask.
If the answer you need is not here, ask us and it will be.
- Do I need a public IP or open ports?
- No. The agent in your cluster opens one outbound connection to Anyport and keeps it open. A cluster behind NAT with every inbound port closed can still serve public HTTPS on your own domain, routed through a gateway we run.
- What do I need before I start?
- If Anyport runs the cluster for you on Anyport Cloud, only Pro, and there is nothing to install. To attach your own, you need a Kubernetes cluster and kubectl access to it. If you do not have a cluster, one command installs k3s, cert-manager and the agent on a fresh machine. A 2 vCPU, 4 GB server is enough to start: Kubernetes and Anyport together use about 1.5 GB of it, and the agent is roughly 100 MB of that. Use 8 GB if you also build container images on the same cluster. One thing to check first: a cluster with no default StorageClass cannot run the managed databases, because their volumes will never be provisioned.
- What happens to my apps if Anyport goes down, or I stop paying?
- They keep running. Everything Anyport creates is a standard Kubernetes object in your cluster, so the workloads, services and ingress do not depend on our control plane to keep serving. What you lose while we are unreachable is the console, not your production. That independence is a property of clusters you attach: a cluster on Anyport Cloud runs on our hardware, so keeping it up is ours to do. If you stop paying, nothing is deleted from a cluster you attach; clusters past the free three are disconnected after 30 days, with an email first, and their apps keep running.
- What can the agent do inside my cluster?
- It runs with full cluster privileges, which is how one-click databases and managed ingress work. It acts on the namespaces Anyport creates, and the terminal feature re-verifies that on the agent side before opening a session. This is worth reading the security page about before you install it.
- Do you hold a SOC 2 or ISO 27001 report?
- Not today. What we publish instead is the substance an audit summarises: what the agent runs with inside your cluster, what data crosses the boundary, how secrets are stored, and how access is controlled, all on one security page you can hand to a reviewer. Two structural points usually matter more to a security team than the badge does. We never receive credentials for your Kubernetes API, and your workloads are ordinary Kubernetes objects that keep serving whether or not our control plane is reachable. If a certification is a hard gate for you, tell us where you are in the process and we will tell you straight whether we can meet it.
- Does my source code or my data leave my infrastructure?
- Builds clone and run on your cluster. Logs and metrics are stored on your hardware and only stream to your browser while you are looking at them. Application traffic reaches us only if you use the gateway to publish a cluster with no public address, and that is opt-in per cluster. On Anyport Cloud all of it, the builds, logs, volumes and traffic, lives on hardware we operate, which is the point of choosing it.
- Is Anyport tied to a cloud provider?
- No. There is no cloud account to connect, no IAM role to create and no provider API we call. If it runs Kubernetes and can make an outbound connection, it works the same way: a hyperscaler, a rented box, or hardware in your own building.
- What does it cost?
- Three clusters are free, with every feature, unlimited members, apps and projects, and no card on file. Pro is $5 a month or $50 a year, two months off, and gives $5 of credit back every month. A cluster you attach past the free three is $2 a month, and every cluster on Anyport Cloud is $5, billed by the hour they exist, with the monthly credit spent first. Compute on clusters you attach is never metered on any plan, because it runs on hardware you already pay for. A cluster on Anyport Cloud, where we run the hardware, is billed from credit for what your apps use, and its own system is never billed. On clusters you attach, the one thing counted is traffic our gateway carries, at 10 GB free and 100 GB on Pro, then $0.02 per GB from credit, up to a spend limit you set. That allowance renews on the day you are billed rather than on the 1st, so it lines up with your billing period. That only applies to a cluster with no public address of its own, where our gateway is what makes it reachable and every byte crosses bandwidth we rent. If your cluster publishes through its own load balancer, traffic goes straight from your visitors to your servers, never reaches us, and is not counted at all.
- Can I get a refund?
- Ask us within 14 days of the charge and we will consider it. Refunds are at our discretion, one per organization, and traffic our gateway has already carried is not refunded, so the case we are really covering is someone who paid, tried it properly and found it did not fit. You should not need it: three clusters are free with no card, so you can find that out before paying anything. Cancelling is separate and always available, takes a click in the billing portal, has no notice period and deletes nothing. The full policy is at anyport.dev/refunds.
- Can I leave?
- Uninstall the agent. Your apps keep running as the ordinary Kubernetes objects they already were, and you can inspect or keep every one of them. A cluster on Anyport Cloud is deleted with everything in it, so duplicate each project onto a cluster of your own first.
01Before you install it
Still deciding?
The security page covers what the agent is allowed to do in your cluster, what crosses the boundary, and where Anyport stands on certification today.