OC Remote vs KubeGlance

OC Remote is a native iPhone and iPad client for the OpenCode server you already run. Keep coding sessions moving when you’re away from your desk—without giving up visibility or control. Connect to stable OpenCode V2 or classic V1 by scanning a pairing code, pasting a URL, using your local network, or connecting securely through Tailscale. With OC Remote, you can: • Watch live session timelines and active runs • Send prompts and choose agents, models, and thinking effort • Answer structured questions and approve permissions • Review changed files and inspect line-by-line diffs • Continue, retry, stop, fork, revert, or unrevert sessions • Mark V2 sessions read or unread across your devices • Archive and restore V2 sessions, and edit saved permission rules • Use project terminals with interactive PTY support • Browse project files and manage integrations and MCP authentication • Dictate prompts on-device, even offline Browse projects, monitor sessions, and stop a run for free. OC Remote Pro unlocks additional remote controls, including session archiving, with an annual auto-renewable subscription. Your OpenCode server stays under your control. OC Remote connects directly to endpoints you configure and provides clear diagnostics when a local, loopback, or Tailscale address needs attention. Terms of Use: https://ocremote.didac.dev/terms Privacy Policy: https://ocremote.didac.dev/privacy OC Remote is an independent client application. It is not affiliated with, endorsed by, or sponsored by OpenCode or Anomaly Innovations, Inc. “OpenCode” is referenced only to describe compatibility with user-configured OpenCode servers.

KubeGlance is a native Kubernetes dashboard for iPhone, iPad, and Mac — a real client for the everyday questions: is my cluster okay, what are my pods doing, and what just changed? Import a kubeconfig and you are looking at your clusters in seconds. No account, no in-cluster agent, no telemetry. KubeGlance talks directly to your Kubernetes API servers with the credentials you already have, and it is read-only by default — you can leave it open against production without a second thought. ONE VIEW, EVERY CLUSTER Enable any set of contexts and pods, workloads, nodes, and events merge into a single live view, each row tagged with its source cluster. Name your clusters and color them — a red "prod" banner follows you everywhere. One unreachable cluster never blanks the others. BUILT FOR INCIDENTS Follow merged logs across all replicas of a workload — or hand-pick any pods, even across namespaces and clusters — in one chronological stream. Structured JSON and nginx lines parse into fields with level filters. Bookmark the line that matters and jump back to it. Search the whole buffer instantly, with regex when you want it. THE DETAILS THAT MATTER - Live pod tables with kubectl-accurate statuses (CrashLoopBackOff and friends) - Workload tables: Deployments, StatefulSets, DaemonSets, Jobs — ready over desired, trouble highlighted - Rollout history with revision compare: see exactly what each deploy changed - Search that speaks kubectl: type namespace:prod status:crash and filters become chips - CPU and memory from metrics-server; history and efficiency (reserved vs used, suggested requests) from Prometheus, VictoriaMetrics or Thanos, auto-detected - Cluster events feed with reason and namespace filters AFTER EVERY DEPLOY The checks you would otherwise run in a terminal, as views that appear only when your cluster has the capability: - GitOps: Flux Kustomizations and Helm releases with applied vs attempted revision and what blocks a reconcile, plus Argo CD apps with sync, health and drift - Autoscaling: HPA and KEDA merged per workload, with fallback, missing metrics and at-max called out, and replica and metric charts - Certificates: cert-manager and TLS secrets sorted by days left - Network: Services with the endpoints actually behind them, plus Ingress routing and Gateway API - Config: ConfigMaps and Secrets with the pods that read them, and which pods still run an older version - Releases: what image is running where, and when it rolled out - CronJobs with a last-run verdict, pod memory as a percent of its limit, and node pools against the provider ceiling - Storage: claims that never bound, volumes nobody mounts, namespace quotas and GPU claims - Resources: browse any kind the API server knows, with kubectl's own columns ALERTS Native notifications for crash loops, restart storms, NotReady nodes, stalled rollouts, failed jobs, expiring certificates, services without endpoints, and pods near their memory limit. Rules are scoped by cluster color, namespace and name patterns. Real-time on the Mac; best-effort background checks on iPhone and iPad. No kubeconfig handy? Tap "Try with a Demo Cluster" and explore with sample data — nothing real is contacted. Auth support: client certificates (mTLS) and bearer tokens, including inline PEM and multi-file kubeconfigs with kubectl merge semantics. KUBEGLANCE PRO — WHAT'S PAID, WHAT'S FREE Connecting your own clusters on iPhone and iPad requires a subscription: KubeGlance Pro. Current pricing and any free trial are shown in the app before you subscribe. Everything else is free — the built-in demo cluster, where you can explore the full app with sample data first, and the entire Mac app, which has no in-app purchases at all. Subscriptions renew automatically unless cancelled at least 24 hours before the end of the current period; manage or cancel anytime in your App Store account settings. Terms of Use: https://kubeglance.com/terms Privacy Policy: https://kubeglance.com/privacy