OCI Marketplace
Origin by Corvus is published as an Oracle Cloud Marketplace stack that deploys a single Linux virtual machine with Origin by Corvus, PostgreSQL, NGINX, and automated TLS. This quick start evaluation option is preferred for customers already using Oracle Cloud Infrastructure (OCI), as it deploys through Resource Manager within your tenancy. It is for evaluation only, not production.
Prefer a hosted sandbox with no local install? Start a 1-hour cloud preview. Prefer to run locally? Use the Docker preview. Already on Azure? Use the Azure Marketplace evaluation VM.
Prerequisites
- An active OCI tenancy with permission to create compute, networking, and public IP resources in a compartment.
- An SSH public key for the instance (password login is not enabled).
- Outbound internet access from the subnet (required for Let's Encrypt and first-boot setup).
What gets deployed
The stack provisions a small, self-contained environment in the compartment you select, including:
- Compute instance (Linux): Runs Origin by Corvus, PostgreSQL, and NGINX from the Origin by Corvus Marketplace image.
- Reserved public IP: Provides a stable address for HTTPS access to your workspace.
- Network security group: Allows inbound HTTP/HTTPS (TCP 80/443) only. The stack NSG does not open SSH from the internet.
- Virtual cloud network (optional): Creates a new VCN and public subnet with an internet gateway, or uses an existing public subnet you select.
- Boot volume: Persistent storage for the operating system, Origin by Corvus data, and configuration.
Step 1: Launch the stack
Go to the Origin by Corvus - Quick Start Evaluation Oracle Cloud Marketplace listing and select Launch Stack.
On the Create stack page, choose a name and the target compartment, accept any Marketplace terms, then continue to configure variables.
Step 2: Virtual Machine Settings
Configure the following:
- Compartment: Where the compute and network resources will be created.
- Availability Domain: Select an availability domain in your region.
- Admin Email (Let's Encrypt): Used when the instance requests a TLS certificate. Use a mailbox you can access.
- Support Email: Contact email shown to end users for troubleshooting.
- SSH Public Key: Paste your public key for Linux access to the instance.
- Compute Shape: For trials, the default VM.Standard3.Flex with 2 OCPUs and 8 GB memory is a good starting point.
Leave Show Advanced Settings off unless you need a custom instance name, boot volume size, or VCN CIDR.
Step 3: Network and Domain Configuration
Configure the following:
- Network Strategy: Prefer Create New VCN and Subnet for evaluation so the stack owns networking end to end. If you choose an existing public subnet, it must allow public IP assignment and inbound TCP 80/443 from the internet. Before you deploy, review that subnet's security lists: OCI evaluates security lists and the stack NSG together, so a security list that allows SSH (TCP 22) still opens SSH even though the stack NSG does not.
- Domain Strategy: For the fastest trial with no DNS setup, select Evaluation Domain (sslip.io). The stack assigns a hostname derived from the public IP (for example,
https://0-0-0-0.sslip.io) and obtains a TLS certificate automatically. - Origin by Corvus Domain (FQDN): Required only when using Bring Your Own Domain. Enter your hostname (for example,
origin.example.com). After apply, create a DNS A record pointing that name to the stack's Public IP Address output; TLS bootstrap retries until DNS resolves correctly.
Step 4: Review and apply
Review the plan, then run Apply in Resource Manager. Infrastructure provisioning usually takes a few minutes. First-boot configuration (TLS and Origin by Corvus startup) can take 5–15 minutes more before HTTPS works reliably.
After the apply completes:
-
Open the stack Outputs.
-
Use Open Origin by Corvus (
origin_url), or build the URL from Origin by Corvus FQDN:https://<origin-fqdn>Evaluation example:
https://0-0-0-0.sslip.io -
If you chose Bring Your Own Domain, follow the DNS Setup output: create the A record to the Public IP Address, then wait for bootstrap to finish.
Use https; the deployment is intended to serve Origin by Corvus over TLS.
Step 5: Open Origin by Corvus and create your administrator
In a browser, go to your HTTPS URL. Origin by Corvus will prompt you to create the first user, which becomes the System Administrator. That account is different from the Linux identity associated with the SSH public key you configured in Step 2.
Congratulations! You've successfully deployed Origin by Corvus for evaluation.
For a high-availability OCI deployment, see Deploy Origin by Corvus on Oracle Kubernetes Engine (OKE).
Next steps
After setting up your Origin by Corvus instance:
- Create your first team and channels
- Invite users to join your workspace
- Explore Origin by Corvus features and integrations
- Review the Application architecture to understand the system better
- Plan your deployment before moving to production
For additional help, visit the Origin by Corvus community forums or the Deployment troubleshooting guide.