General#
What does EJO Cloud host, and what do I run?#
EJO Cloud runs your organization's EJO console and API for you (for example acme.ejocloud.com). Your pipelines are run by agents on your own infrastructure: a Kubernetes cluster or a server with Docker. See Installing an agent.
Do I need to open inbound ports for the agent?#
No. The agent connects to EJO Cloud over HTTPS by itself and picks up jobs. The machine it runs on only needs outbound internet access to your organization's address.
Where is my code built?#
Your repository is cloned, built and deployed where your agent runs. EJO talks to your SCM (GitHub, GitLab or Azure DevOps) to read .ejo and pipeline files and to post commit statuses and pull request comments.
Where is my data stored?#
EJO Cloud data is stored on servers in Turkey. The privacy notice on the signup page has the details.
Which Git providers are supported?#
GitHub, GitLab (gitlab.com or a self-managed GitLab reachable from the internet) and Azure DevOps Services (dev.azure.com). You can use all three together in one organization. GitHub connects through the shared EJO Cloud GitHub App; on GitLab and Azure DevOps, events arrive through webhooks you save under Settings > Webhooks, and cloning, statuses and the merge gate need a token. Azure DevOps Server running on your own servers is not supported. See Connect your source control.
Do I need a GitHub account to use GitLab or Azure DevOps?#
No. The GitHub App is only for GitHub repositories. To sign up and sign in, an e-mail and password or a Google account is enough; Continue with GitHub is only a sign-in method and has nothing to do with connecting repositories.
Account and access#
I forgot my password.#
An admin in your organization can set a new password for you with Set password on the Users page. If you are the organization's only admin, write to destek@ejocloud.com from the organization owner's e-mail address.
A teammate cannot sign in with Google.#
Google or GitHub sign-in never creates an account. An admin must first add them with their verified e-mail address as the username. See Google and GitHub sign-in.
Can I require 2FA for everyone?#
Yes. Turn on Require two-factor authentication on Settings > Security. See Two-factor authentication.
Pipelines#
Should I keep the pipeline in the repository or in the console?#
Either works. Keeping ejo.yaml in the repository means changes are reviewed in pull requests; pick From repo — ejo.yaml is source of truth as the binding's Pipeline source. See Triggers and bindings.
Can pull requests from forks reach my secrets?#
No. For pull requests (merge requests on GitLab) opened from forks, the fork's ejo.yaml is not used, and no secret values, clone credentials or OIDC tokens are handed out. This applies to all three SCMs.
Do I have to copy my secrets into EJO?#
No. If you use Vault, AWS Secrets Manager, Azure Key Vault or CyberArk, connect it as a secret store; the agent reads the values with its own identity and EJO never sees them. See Secrets and variables.
Plans and billing#
Is EJO Cloud free?#
The Community plan is free and allows up to 4 users. The Team plan is paid and allows up to 25 users. See Plans and billing.
Will my deployments stop if I do not pay?#
No. Deployments are never stopped because of billing. If the Team period and its grace period end, the organization goes back to the Community plan; your data is not deleted.
Does the Team plan renew automatically?#
No. Before the period ends, the organization owner gets a payment link by e-mail; you renew by paying through that link.
Data and privacy#
How do I have my account and data deleted?#
Write to kvkk@ejocloud.com from the organization owner's e-mail address. Use the same address for your other requests under the Turkish data protection law (KVKK). See Support.
What happens to the details of a signup that is not approved?#
No account is created for a signup that is not approved, and the details given are deleted within 30 days.