Deployment editions¶

GeoJibe is one codebase and one binary. Shared, Dedicated, and On-Site are installation editions, not separate products.

Set the edition with ENCIVA_DEPLOYMENT. Unknown values are rejected at startup. If the variable is unset, GeoJibe uses On-Site so existing self-hosted installs do not suddenly offer public signup or a 3-Job limit.

Edition	Typical host	Public signup	Users	Saved Jobs
Shared	`app.geojibe.com`	Yes (email verification)	1 per account	3
Dedicated	A dedicated GeoJibe VM	No	Unlimited	Unlimited
On-Site	Customer infrastructure	No	Unlimited	Unlimited

ENCIVA_DEPLOYMENT=shared
ENCIVA_DEPLOYMENT=dedicated
ENCIVA_DEPLOYMENT=onsite

Shared¶

Hosted GeoJibe. Customers create an account with email and password. They must verify email before sign-in. Each account has one user and at most three saved Jobs. Disabled Jobs count. Deleting a Job frees a slot. One-off Canvas runs, Recipes, and Sources/Destinations do not count.

Shared requires:

ENCIVA_PUBLIC_URL (absolute https://… URL used in verification links — never taken from the request Host header)
Installation SMTP (ENCIVA_SMTP_HOST and ENCIVA_SMTP_FROM) so verification mail can be sent

The first administrator is not created by customer signup. Signup users are ordinary account members. They cannot manage other customers, SMTP, or server settings.

If the user database is empty, Shared may start without ENCIVA_BOOTSTRAP_ADMIN_*. Optional bootstrap credentials still create an installation administrator.

Dedicated¶

A dedicated GeoJibe installation. There is no public Create Account page. Create the first administrator with ENCIVA_BOOTSTRAP_ADMIN_USERNAME and ENCIVA_BOOTSTRAP_ADMIN_PASSWORD when the database is empty. There is no Shared 3-Job or 1-user limit.

On-Site¶

Installed on customer infrastructure. Same application as Dedicated: no public signup by default, unlimited saved Jobs and users, first administrator provisioned through bootstrap. On-Site does not contact a GeoJibe license server.

Personal Access Tokens and /api/v1 belong to the local user database on every edition. The CLI and SDK will call this installation's API with GEOJIBE_URL and GEOJIBE_TOKEN.

SMTP¶

One server-level mail configuration is used for account verification, Job notifications, and future account email. See Configuration and Job Notifications. Do not put SMTP passwords in logs.

Upgrades¶

Changing ENCIVA_DEPLOYMENT on an existing database does not provision a new VM. Moving a Shared customer to Dedicated is an infrastructure step, not a flag flip inside the Shared database.