Projects & applications
Projects organize related applications. Workspace and application views give you overview, deployments, logs, environment, domains, connections, activity, and settings — and status stays visible even when an operation fails.
PLATFORM
One platform, from first deploy to daily operations.
iDeployed brings deployment, configuration, domains, logs, and application operations into one coherent experience. You work with projects, applications, deployments, services, connections, domains, storage, and logs — never with Kubernetes objects, Linux user IDs, or ingress controllers.
- STEP 01
Bring your code or image
Connect a GitHub repository, bring a container image from a supported registry, or start from a curated template.
- STEP 02
Choose how it runs
Set the port, environment, and exposure — public with HTTPS, or private with an internal address only.
- STEP 03
Deploy, connect, operate
Follow build and deployment progress, connect private services explicitly, and operate everything from one dashboard.
WHAT YOU WORK WITH
The whole lifecycle, at the level of your application.
Configuration & secrets
Environment variables and project-scoped registry connections, with secret values protected and masked. The normal workflow never reveals stored values back to the browser. Configuration applies through an explicit deployment action.
Domains & TLS
Public applications receive a platform HTTPS address on ideployed.app — or connect your own domain, follow the DNS instructions, and watch verification progress. Routing and certificate lifecycle are handled for you.
Private services & connections
Choose public or private exposure per application. Private services have an internal address and no public route. You explicitly connect application A to private application B, on B’s declared port.
Logs & deployment history
Build logs, runtime logs, deployment stages, history, activity, and intelligible failures — with resource usage and health understandable alongside. Follow a change from source to running application.
Persistent storage
Persistent volumes are part of the stateful-template experience: data survives container replacement. Persistence is not the same as backup, replication, or disaster recovery — and we say so.
Work from coding tools
CLI/MCP-based access from the tools you already use — Codex, Claude Code, Cursor, GitHub Copilot in VS Code, Gemini CLI, Cline. Inspect an application, deploy a version, read logs, or choose a rollback without leaving your workflow.
Account security
Email verification, authenticator-based two-factor authentication, recovery codes, session management and revocation, and guarded account deletion — the full account lifecycle, done properly.
A MENTAL MODEL YOU CAN TRUST
Saved. Running. About to change.
Three states that stay distinct — so a release never surprises you.
01
Saved configuration
Your environment variables and settings. Saving does not restart anything.
02
Running version
The exact image artifact currently serving traffic — recorded by digest, not just by tag.
03
Release action
Redeploy current version, deploy saved image, or roll back — each with a predictable outcome.
Rolling back an image does not restore a database or old environment variables — and the product tells you so before you act.
KEEP EXPLORING
YOUR NEXT CHAPTER
Good ideas deserve
to be out there.
Bring your code. Make something people can use.