Origin by Corvus — Self-Hosted Platform Requirements & Deployment Specification
Platform: Origin by Corvus
Provider: Quantum Tiger (Morning Bay Technology Pvt. Ltd.)
Official Website: https://quantumtiger.in
Support & Inquiries: contact@quantumtiger.in | support@quantumtiger.in
1. Overview & Architectural Philosophy
Origin by Corvus is a sovereign, secure, self-hosted team collaboration and real-time messaging platform engineered by Quantum Tiger (Morning Bay Technology Pvt. Ltd.). Designed for on-premise, private cloud, and air-gapped corporate networks, Origin by Corvus guarantees complete data sovereignty, granular administrative control, and high-performance communication.
Origin by Corvus is delivered as a standalone, self-contained application. All components—core application, database, storage, calling engine, and email relay—are hosted and managed entirely within the customer's own infrastructure. There are no external cloud dependencies, central relays, or phone-home services.
2. Supported Hardware & CPU Architectures
Origin by Corvus runs as a compiled 64-bit native Linux binary and inside standard container engines (Docker, Podman, Kubernetes).
2.1 Supported CPU Architectures
| Architecture | Identification | Support Status | Notes |
|---|---|---|---|
| x86_64 / amd64 | 64-bit Intel / AMD (x64) | Supported (Recommended) | Standard for enterprise server hardware, VMware, KVM, Hyper-V, and cloud VMs (AWS EC2, GCP Compute Engine, Azure VMs, Bare Metal). |
| arm64 / aarch64 | 64-bit ARM | Supported | Supported on 64-bit ARM server platforms, including AWS Graviton, Ampere Altra, Apple Silicon (virtualized containers), and 64-bit Linux ARM environments. |
| x86 (32-bit / i386) | 32-bit Intel / AMD | Not Supported | 32-bit architectures are not supported due to modern runtime and memory requirements. |
| ARM 32-bit (armhf / armv7) | 32-bit ARM | Not Supported | 32-bit ARM is not supported. |
2.2 Server Hardware Sizing Guidelines
Hardware requirements depend on active concurrent users, channel count, and file upload volume:
| Deployment Scale | Active Team Members | CPU / Virtual Cores | Memory (RAM) | Database Storage (SSD) | File Storage Volume | Voice & Screen Share Load |
|---|---|---|---|---|---|---|
| Small Team | 1 – 100 members | 2 vCPUs | 4 GB RAM | 20 GB SSD | 50 GB+ (based on usage) | Up to 10 concurrent in calls |
| Standard Team | 100 – 250 members | 4 vCPUs | 8 GB RAM | 50 GB SSD | 150 GB+ (based on usage) | Up to 30 concurrent in calls |
Storage & Network Specifications:
- Operating System & Database: Enterprise Solid State Drives (NVMe or enterprise SSD) are required for optimal database index lookups and responsive WebSocket state synchronization.
- File & Media Storage: Can reside on a local directory mount, network-attached storage (NFS), or a self-hosted S3-compatible object store (e.g., MinIO, Ceph).
- Default Upload Size Limit: 100 MB per file attachment (configurable up to 4 GB by System Administrators).
- Network Bandwidth for Calls: Allow ~50 kbps per audio stream (Opus) and 500 kbps to 1.5 Mbps per active screen share stream (1080p). Ensure UDP port 8443 is open on server firewalls.
3. Mandatory Self-Hosted Infrastructure Components
Origin by Corvus is an independent, 100% self-hosted system. Deploying organizations must provision and maintain the following infrastructure components:
3.1 Core Application Server
- Service: Origin by Corvus application binary.
- Deployment Format: Container (Docker Engine 24+, Docker Compose v2+, Podman, Kubernetes) or native Linux systemd service.
- Listening Port: Default internal HTTP/WebSocket port
8065.
3.2 Self-Hosted Database Management System (DBMS)
Origin by Corvus requires a dedicated relational database:
- Supported Engines:
- PostgreSQL: 14.x, 15.x, 16.x, or 17.x (Strongly Recommended for native full-text indexing and high concurrency).
- MySQL: 8.x+.
- Requirements:
- Dedicated database instance and non-root user with full schema privileges.
- Character Set / Encoding:
UTF-8. - Collation:
en_US.UTF-8(or standardC/UTF-8). - The database is completely self-managed by the licensee; Quantum Tiger provides no cloud database hosting.
3.3 Self-Hosted SMTP Email Relay
- Purpose: Used for sending team invitations, password reset verification links, account creation verifications, and offline mention email digests.
- Requirements: A dedicated corporate SMTP server or relay (e.g., Postfix, Exim, Amazon SES, SendGrid, or internal corporate mail gateway) supporting TLS (Port 587 STARTTLS or Port 465 SSL).
3.4 Reverse Proxy & SSL/TLS Termination
- Supported Proxies: Nginx, Traefik, HAProxy, Caddy, Apache 2.4, or AWS Application Load Balancer (ALB).
- Requirements:
- Port 80 (HTTP) redirecting to Port 443 (HTTPS).
- Valid TLS 1.2 or TLS 1.3 certificate (Let's Encrypt or internal organizational PKI).
- WebSocket upgrade support (
Connection: Upgrade,Upgrade: websocket) forwarding traffic to internal port8065.
3.5 WebRTC Voice & Screen Sharing Infrastructure (Origin Calls Requirements)
Origin by Corvus features an embedded, sovereign real-time voice and screen sharing service (Origin Calls). To self-host audio and screen sharing, the following networking requirements apply:
- Signaling Traffic (WebSocket):
- Operates entirely over your existing secure HTTPS / WebSocket connection (Port 443 / internal Port 8065). No separate signaling server or extra subdomains are required.
- Media Traffic (RTP/SRTP Audio & Video Streams):
- UDP Port 8443 (Required): The Origin server listens on UDP Port 8443 for incoming encrypted voice and screen share media packets. This port must be forwarded/opened in your cloud security groups (AWS Security Groups, Azure NSG, GCP Firewall) and host firewall (
ufw allow 8443/udporfirewall-cmd --add-port=8443/udp). - TCP Port 8443 (Fallback): Can be enabled in System Console > Plugins > Origin Calls to allow clients on strict networks that block outgoing UDP to connect over TCP.
- UDP Port 8443 (Required): The Origin server listens on UDP Port 8443 for incoming encrypted voice and screen share media packets. This port must be forwarded/opened in your cloud security groups (AWS Security Groups, Azure NSG, GCP Firewall) and host firewall (
- NAT Traversal & STUN / TURN Server (coturn):
- When a TURN Server is NOT Required (LAN / VPN Deployments): If all participating team members connect from within the same flat corporate network, local office LAN, or over an enterprise VPN (e.g. WireGuard, OpenVPN, Tailscale), no TURN server is required. Clients connect directly to the server on UDP port 8443.
- When a TURN Server IS Required (Remote WAN Deployments): If team members work remotely across the public internet from residential Wi-Fi, cellular hotspots, or behind symmetric enterprise NAT routers that block peer-to-peer UDP packet traversal, the deploying organization must host a STUN/TURN server (such as open-source coturn).
- Recommended TURN Ports:
- Port 3478 (UDP & TCP): Standard STUN / TURN port.
- Port 5349 (TLS): TURNS encrypted relay port.
- Configuration: The TURN server address, shared authentication secret, and credential lifetime are configured in System Console > Plugins > Origin Calls.
- Bandwidth & Codec Specifications:
- Audio: High-fidelity Opus codec streaming at ~50 kbps per participant with built-in acoustic echo cancellation and noise suppression.
- Screen Sharing: Adaptive VP8 / H.264 video codec streaming at 500 kbps to 1.5 Mbps per active presenter at 1080p resolution.
4. Client Platform & Access Requirements
Origin by Corvus is engineered as a responsive, modern web application accessible across all standard enterprise client devices without mandatory workstation software installation.
4.1 Desktop Web Browsers
Users access Origin by Corvus through any modern evergreen web browser on Windows, macOS, and Linux:
| Browser | Minimum Version | Operating System |
|---|---|---|
| Google Chrome | Latest 3 major releases | Windows, macOS, Linux |
| Mozilla Firefox | Latest 3 major releases / ESR | Windows, macOS, Linux |
| Apple Safari | Safari 17+ (macOS 14+) | macOS |
| Microsoft Edge | Latest 3 major releases | Windows, macOS |
4.2 Mobile Browsers & Progressive Web App (PWA)
- Supported Mobile Browsers: Google Chrome for Android and Apple Safari for iOS.
- Progressive Web App (PWA): Users can install Origin by Corvus directly from their mobile or desktop browser via the "Install App" or "Add to Home Screen" prompt. The PWA delivers a windowed application interface, home-screen launch icons, persistent sessions, and native OS notifications.
4.3 Client Security & Isolation Policy
Origin by Corvus enforces an organizational client-isolation policy:
- Access is provided exclusively via modern web browsers and installable Progressive Web Apps (PWA).
- External, unmanaged third-party client applications are restricted and disabled by the server to prevent data leakage, enforce corporate access boundaries, and preserve organizational security.
5. Enabled Feature Catalog (Built-In Capabilities)
Origin by Corvus is distributed as a fully functional, self-contained collaboration platform. All listed features are enabled and operational out-of-the-box:
5.1 Real-Time Messaging & Channel Organization
- Public Channels: Open channels accessible to all members of a team for transparent collaboration.
- Private Channels: Restricted-membership channels for confidential department discussions.
- Direct Messages (1:1): Private, direct communication between two individual colleagues.
- Group Messages: Multi-party direct messaging with up to 7 participants.
- Threaded Discussions: Collapsible message reply threads to keep complex conversations organized without cluttering channel streams.
- Unlimited Message History: Full conversation history stored directly in your self-hosted database without artificial message retention limits.
- Rich Text & Formatting: Full GitHub-flavored Markdown support, including bold, italics, tables, ordered/unordered lists, blockquotes, and code blocks with syntax highlighting.
- Custom Emoji & Reactions: Complete system emoji picker plus custom organization emoji uploads and one-click reaction responses.
- Bookmarking & Flagging: Save important messages for later reference, and flag posts for follow-up.
- Message Pinning: Pin critical messages and reference materials to the channel info sidebar for quick team access.
- File & Media Previews: Drag-and-drop file uploads with inline previews for images, video playback, audio clips, PDFs, and text documents.
- Rich @Mentions: Target notifications using
@username, notify everyone active in a channel with@here, or address all channel members with@channel/@all. - User Presence & Status: Real-time presence indicators (Online, Away, Do Not Disturb, Offline) and customizable status messages with custom emoji.
- Full-Text In-Database Search: Native database-indexed search across all channels, messages, and uploaded file metadata, with filtering operators (
from:,in:,on:,before:,after:).
5.2 Workspaces & Team Collaboration
- Team Workspaces: Dedicated collaborative spaces with independent channel rosters, integrations, and member directories.
- Capacity: Sized for teams with up to 250 active members per team workspace.
- Collapsible Sidebar Categories: Customizable channel grouping (Channels, Direct Messages, Favorites, and custom user-created categories) with drag-and-drop ordering.
5.3 Extensibility & Developer Integrations
- Incoming Webhooks: Post automated notifications, build status alerts, monitoring alerts, and data streams from external tools into channels via HTTP POST.
- Outgoing Webhooks: Trigger external web services and workflows automatically when messages match specific keyword triggers.
- Custom Slash Commands: Create custom
/commands that send HTTP requests to internal services and post formatted responses back to channels. - Interactive Message Actions: Build interactive messages with clickable action buttons, dropdown menus, and modal dialogs.
- Bot Accounts: Dedicated bot user accounts with granular permissions for automated bots and notification assistants.
- Personal Access Tokens (PATs): Generate secure tokens for programmatic scripts and CLI automation without sharing account passwords.
- REST API (v4): Comprehensive, fully documented HTTP REST API covering all platform operations (users, channels, messages, files, teams).
5.4 Authentication & Security Controls
- Native Authentication: Secure email and username authentication with salted bcrypt password hashing.
- Multi-Factor Authentication (MFA / 2FA): Built-in Time-based One-Time Password (TOTP) authentication compatible with Google Authenticator, Authy, Microsoft Authenticator, and 1Password.
- Password Complexity Policies: Enforce minimum password lengths and require combinations of uppercase letters, lowercase letters, numbers, and symbols.
- Session Management: Configurable session durations, idle timeouts, and administrative ability to revoke user sessions on demand.
- GitLab OAuth: Standard OAuth 2.0 single sign-on integration with self-hosted or cloud GitLab instances.
5.5 System Administration & Operations (System Console)
- Web-Based Management Console: Comprehensive graphical administration dashboard for complete platform governance.
- User Lifecycle Management: Create, invite, deactivate, or reactivate user accounts; promote users to System Admin or Team Admin; reset passwords.
- Channel Administration: View, archive, unarchive, and modify channels and memberships across the organization.
- Custom Branding & Localization: Configure custom server display name, custom description, custom login page header and footer text, and brand logos.
- Storage Configuration: Configure storage backend (local filesystem directory or S3-compatible storage), set maximum file sizes, and configure allowed MIME types.
- Server Health & Logging: Real-time server logging with severity levels (DEBUG, INFO, WARN, ERROR), log rotation, and server uptime statistics.
- Internationalization: Native localization support with 20+ built-in language translations.
5.6 Integrated Voice & Screen Sharing Module (Origin Calls)
- Embedded In-Channel Calling: One-click WebRTC voice calling directly inside public channels, private channels, and direct messages without third-party meeting links.
- Screen & Window Sharing: Live high-framerate screen sharing and individual application window casting during active calls.
- Self-Contained Sovereign Media Routing: Media flows peer-to-peer or through your self-hosted WebRTC gateway; no third-party cloud audio/video relays are used. See Section 3.5 for network and firewall requirements (UDP 8443, coturn).
- Participant Controls: Real-time participant roster, mute/unmute management, raise hand indicators, and active speaker visual highlighting.
- Call State Synchronization: Active call banners and join/leave status indicators dynamically displayed in channel headers.
5.7 Integrated Project & Task Management Module (Origin Boards)
- Visual Project Workspace: Full-featured project and task management embedded directly in channels for contextual collaboration.
- Multiple Board Layouts:
- Kanban Board: Drag-and-drop task card pipeline organized by status, priority, or custom categories.
- Table / Spreadsheet Grid: Dense tabular data entry with sortable columns and custom formula calculations.
- Calendar View: Monthly and weekly task deadlines mapped to calendar dates.
- Gallery View: Card visual showcase optimized for media assets, design comps, and document attachments.
- Rich Card Detail: Task cards support Markdown descriptions, subtask checklists, multi-select tags, date ranges, file attachments, and discussion comments.
- Pre-Built Templates: Includes industry-standard templates for Software Sprint Planning, Bug & Defect Tracking, Product Roadmaps, Team Onboarding, and Meeting Agendas.
- Channel Access Inheritance: Board access permissions automatically synchronize with channel membership, ensuring data confidentiality.
5.8 Integrated Process & Incident Automation Module (Origin Workflows)
- Structured Runbooks & Playbooks: Repeatable standard operating procedures (SOPs) and incident management runbooks connected directly to team channels.
- Stage Checklists & Milestones: Multi-stage operational checklists with assigned task owners, automated task transitions, and slash command triggers.
- Automated Stakeholder Broadcasting: Automatically dispatches formatted status updates and milestone summaries to designated channels upon incident progress.
- Chronological Timeline & Retrospectives: Automatically compiles a timestamped audit trail of all actions, decisions, and chat messages during an operational event for post-mortem analysis.
- Workflow Triggers: Launch workflows automatically via slash commands (
/playbook run), incoming webhooks, or keyword triggers.
5.9 Native Scheduled Messaging & Draft Queues
- Scheduled Post Delivery: Native capability to compose messages and schedule automated delivery for a specific date and time without external plugins.
- Recurring Post Intervals: Configure scheduled announcements to recur on daily, weekly, or custom calendar frequencies.
- Draft & Queue Management: Dedicated sidebar panel displaying all unsent drafts and pending scheduled posts, allowing in-flight editing, rescheduling, or cancellation prior to broadcast.
- Autonomous Server Execution: Handled natively by the backend server scheduler job (
ScheduledPostJob), ensuring reliable delivery even if the client is offline.
6. Environment Configuration Modules & Maximum Limits
Origin by Corvus provides granular administrative governance through the System Console > Environment interface. System Administrators can tune each subsystem to its highest possible operating capacity based on organizational requirements and server hardware sizing.
6.1 Environment Module Limits Summary
| Environment Panel | Parameter / Config Key | Default Setting | Highest Possible Ceiling | Operational & Hardware Guidance |
|---|---|---|---|---|
| Web Server | ServiceSettings.MaximumPayloadSizeBytes | 300,000 (~300 KB) | 104,857,600 Bytes (100 MB) | Maximum size for JSON/REST API payloads. Set higher for heavy webhook data payloads. |
| Web Server | ServiceSettings.ReadTimeout | 300 seconds | 3,600 seconds (1 hour) | Maximum time allowed from connection accepted to request body read completion. |
| Web Server | ServiceSettings.WriteTimeout | 300 seconds | 3,600 seconds (1 hour) | Maximum time allowed from request processing to complete response delivery. |
| Web Server | ServiceSettings.MaximumLoginAttempts | 10 attempts | Unlimited / 1,000 attempts | Number of failed login attempts allowed before IP/account lockout triggers. |
| Web Server | ServiceSettings.TLSStrictTransportMaxAge | 63072000 (2 years) | 315,360,000 seconds (10 years) | Enforces Strict-Transport-Security (HSTS) max-age header across browsers. |
| Database | SqlSettings.MaxOpenConns | 300 connections | 1,000 – 2,000+ connections | Aligns with PostgreSQL/MySQL max_connections allocation for high-concurrency workloads. |
| Database | SqlSettings.MaxIdleConns | 20 connections | 300 – 500 connections | Maintains pre-warmed idle connection pool to eliminate handshake latency on traffic bursts. |
| Database | SqlSettings.QueryTimeout | 30 seconds | 300 seconds (5 minutes) | Timeout limit for transactional SQL queries before aborting. |
| Database | SqlSettings.AnalyticsQueryTimeout | 30 seconds | 600 seconds (10 minutes) | Timeout ceiling for long-running statistical aggregation and analytics queries. |
| Database | SqlSettings.ConnMaxLifetimeMilliseconds | 3,600,000 ms (1 hr) | Unlimited (0) or 86,400,000 ms | Connection recycling lifetime in pool (0 keeps connections alive indefinitely). |
| Database | SqlSettings.MigrationsStatementTimeoutSeconds | 1,000 seconds | 7,200 seconds (2 hours) | Timeout allowance for database schema migrations and indexing operations. |
| File Storage | FileSettings.MaxFileSize | 104,857,600 (100 MB) | 4,294,967,296 Bytes (4 GB) | Maximum attachment file size. Ensure matching proxy client_max_body_size. |
| File Storage | FileSettings.MaxImageResolution | 33,177,600 (8K UHD) | 100,000,000+ Pixels (~100 MP) | Maximum allowable image resolution for server-side thumbnail rendering and previews. |
| File Storage | FileSettings.MaxImageDecoderConcurrency | -1 (Auto / All Cores) | Unlimited (-1) or Core Count | Concurrent threads dedicated to image decompression and rendering. |
| File Storage | FileSettings.AmazonS3UploadPartSizeBytes | 5,242,880 (5 MB) | 104,857,600 Bytes (100 MB) | Multipart upload part size for S3/MinIO/Ceph object storage backends. |
| Image Proxy | ImageProxySettings.ImageProxyType | local | Full Local Caching Proxy | Renders external Markdown images through an internal caching proxy to prevent SSRF and IP leakage. |
| SMTP | EmailSettings.ConnectionSecurity | TLS / STARTTLS | TLS 1.3 / Port 465 / 587 | Enterprise mail relay with mandatory encryption and certificate verification. |
| Rate Limiting | RateLimitSettings.MemoryStoreSize | 10,000 tracked keys | 500,000 tracked keys | Maximum distinct client IP addresses and user tokens tracked concurrently in memory (~25-50 MB RAM). |
| Rate Limiting | RateLimitSettings.PerSec | 10 requests/sec | 1,000 requests/sec | Maximum continuous API requests allowed per second per tracked user/IP. |
| Rate Limit | RateLimitSettings.MaxBurst | 100 requests | 2,000 requests | Maximum burst request allowance beyond the per-second rate limit. |
| Logging | LogSettings.FileLevel | INFO | DEBUG (Highest Verbosity) | Captures detailed diagnostic events, SQL trace logging, and webhook payloads. |
| Logging | LogSettings.MaxFileSizeMB | 100 MB | 1,000 MB (1 GB) | Log file size threshold before automatic rotation and compressed archiving. |
| Session Lengths | ServiceSettings.SessionLengthWebInHours | 720 hours (30 days) | 87,600 Hours (10 Years) | Maximum active session duration for web browsers and PWAs using credentials or LDAP. |
| Session Lengths | ServiceSettings.SessionLengthMobileInHours | 720 hours (30 days) | 87,600 Hours (10 Years) | Maximum active session duration for mobile web and PWA clients. |
| Session Lengths | ServiceSettings.SessionLengthSSOInHours | 720 hours (30 days) | 87,600 Hours (10 Years) | Maximum active session duration for GitLab / OAuth 2.0 single sign-on sessions. |
| Session Lengths | ServiceSettings.SessionCacheInMinutes | 10 minutes | 1,440 Minutes (24 Hours) | Duration active user session tokens remain cached in memory without database queries. |
| Session Lengths | ServiceSettings.SessionIdleTimeoutInMinutes | 0 (Disabled / Unlimited) | 525,600 Minutes (1 Year) | Idle timeout threshold (minimum: 5 minutes when enabled; 0 allows continuous access). |
| Performance Monitoring | MetricsSettings.ListenAddress | :8067 | Dedicated Monitoring Port | Exposes native Prometheus metrics for CPU, RAM, Goroutines, DB latency, and WebSocket concurrency. |
| Developer | ServiceSettings.AllowedUntrustedInternalConnections | Empty (Blocked) | All Private Subnets | Whitelists internal CIDR ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) for intranet webhooks. |
6.2 Detailed Specifications by Environment Subsystem
1. Web Server (ServiceSettings)
- Site URL & Network Binding: Origin by Corvus binds to all network interfaces (
:8065default) or a dedicated IP address (127.0.0.1:8065when behind an Nginx reverse proxy). - Maximum Payload Size (
MaximumPayloadSizeBytes): Controls the byte ceiling for incoming HTTP API request payloads. While standard JSON messages require under 100 KB, this can be increased up to 100 MB (104857600bytes) to support bulk programmatic data imports and large REST integration posts. - Read / Write Timeouts (
ReadTimeout,WriteTimeout): Both parameters default to300seconds (5 minutes) and can be set up to 3,600 seconds (1 hour) to ensure long-running client operations and large file attachments over high-latency networks do not experience premature connection termination. - GZIP Compression:
WebserverMode: gzipcompresses all static text, CSS, JavaScript, and JSON payloads, reducing bandwidth consumption by up to 70%.
2. Database (SqlSettings)
- Database Engine: PostgreSQL 14+ (or MySQL 8+) operating in
UTF-8encoding. - Connection Pool Capacity:
MaxOpenConns: Can be raised to 1,000 – 2,000+ on enterprise database clusters to handle massive concurrent transaction volume without query queuing.MaxIdleConns: Can be configured up to 300 – 500 idle connections, keeping warm sockets readily available to handle immediate load spikes.
- Connection Lifetime & Recycling:
ConnMaxLifetimeMilliseconds: Defaults to3,600,000ms (1 hour); setting to0allows connections to remain open indefinitely, reducing TCP connection renegotiation.ConnMaxIdleTimeMilliseconds: Defaults to300,000ms (5 minutes); configurable up to 3,600,000 ms (1 hour).
- Query & Analytics Ceilings:
QueryTimeout: Can be set up to 300 seconds (5 minutes) for deep historical searches across years of messages.AnalyticsQueryTimeout: Can be configured up to 600 seconds (10 minutes) for comprehensive organization-wide statistical rollups.
3. File Storage (FileSettings)
- Storage Drivers:
local: Direct NVMe / SSD local directory mount (default:./data/) or NFS mount.amazons3: Compatible with AWS S3, MinIO, Ceph, Cloudian, and pure S3-compliant storage clusters.azureblob: Compatible with Azure Blob Storage (Commercial, Government, and Custom endpoints).
- Maximum File Attachment Ceiling (
MaxFileSize):- Configurable up to 4 GB (
4294967296bytes). To enable large file uploads, ensure your reverse proxy (e.g. Nginx) hasclient_max_body_size 4096M;configured.
- Configurable up to 4 GB (
- Maximum Image Resolution (
MaxImageResolution):- Default:
33,177,600pixels (8K UHD: 7680 Ã - 4320). - Can be increased to 100,000,000+ pixels (~100 Megapixels) for ultra-high-resolution architectural blueprints, design composites, and panoramic scans.
- Default:
- Image Decoder Concurrency (
MaxImageDecoderConcurrency):- Setting to
-1automatically parallelizes image decompression across all available CPU cores on the host.
- Setting to
4. Image Proxy (ImageProxySettings)
- Local Image Proxying: Built-in proxy (
local) intercepts all Markdown images pasted into channels, fetching remote images through the server. - Privacy & Security Protection: Shields end-user IP addresses from external tracking servers, prevents Mixed Content HTTPS browser warnings, and validates MIME types to protect against Server-Side Request Forgery (SSRF).
5. SMTP Email Relay (EmailSettings)
- Connection Security: Supports
TLS(Port 465 SSL/TLS) andSTARTTLS(Port 587 STARTTLS) with rigorous TLS certificate validation. - Delivery Reliability: Supports authentication via username/password, API keys (e.g. AWS SES, SendGrid), and local network IP-whitelisted mail relays (e.g. Postfix).
- Automated Security Notifications: Includes automated 12-hour background checks delivering critical administrative security alerts to system administrator emails.
6. Rate Limiting (RateLimitSettings)
- Memory Store Capacity (
MemoryStoreSize):- Tracks client states in RAM. Can be increased from
10,000to 500,000 tracked keys, allowing large organizations to maintain individual rate-limiting metrics for hundreds of thousands of distinct IP addresses and user tokens with negligible memory overhead (~25-50 MB).
- Tracks client states in RAM. Can be increased from
- Throughput & Burst Ceilings (
PerSec,MaxBurst):PerSec: Can be increased up to 1,000 requests/sec for high-frequency internal bot integrations and automated data pipelines.MaxBurst: Can be increased up to 2,000 requests to absorb instantaneous connection spikes when hundreds of users open their web clients at the start of the workday.
- Tracking Granularity: Can vary rate limits by remote IP (
VaryByRemoteAddr), user authentication token (VaryByUser), or trusted reverse proxy headers (VaryByHeader:X-Forwarded-For,X-Real-IP).
7. Logging (LogSettings)
- Severity Levels:
DEBUG(comprehensive event tracing),INFO(standard operational logs),WARN, andERROR. - Log Rotation & Archiving:
- Files are automatically rotated when reaching 100 MB (or up to 1,000 MB / 1 GB) and archived as timestamped serial files (
origin.YYYY-MM-DD.001.gz).
- Files are automatically rotated when reaching 100 MB (or up to 1,000 MB / 1 GB) and archived as timestamped serial files (
- Structured JSON Logging: Both console and file logging support machine-readable JSON formatting (
ConsoleJson: true,FileJson: true), enabling seamless ingestion into centralized logging pipelines (e.g., Elasticsearch, Splunk, Graylog, Grafana Loki). - Diagnostics & SQL Tracing: Supports full SQL statement logging (
SqlSettings.Trace: true) and complete HTTP body capture for incoming webhooks for deep troubleshooting.
8. Session Lengths (ServiceSettings)
- Maximum Session Lifespan:
SessionLengthWebInHours: Web browser and PWA session length can be configured up to 87,600 hours (10 years) or 8,760 hours (1 full year), eliminating repeated login prompts on secure organizational workstations.SessionLengthMobileInHours: Mobile browser and PWA session length can likewise be set up to 87,600 hours (10 years).SessionLengthSSOInHours: Single Sign-On (GitLab / OAuth) sessions can be set up to 87,600 hours.
- Session Cache Duration (
SessionCacheInMinutes):- Can be extended up to 1,440 minutes (24 hours) to cache authenticated session validation tokens in server RAM, significantly reducing database read queries.
- Idle Timeout Control (
SessionIdleTimeoutInMinutes):- Set to
0(default) for indefinite continuous sessions as long as the session duration is valid. - When enabled, minimum timeout is
5minutes, and can be configured up to 525,600 minutes (1 year).
- Set to
- Session Extension on Activity (
ExtendSessionLengthWithActivity):- When enabled (
true), every user interaction resets the session timer, ensuring that actively collaborating team members are never unexpectedly logged out mid-work.
- When enabled (
- Security Invalidation (
TerminateSessionsOnPasswordChange):- When enabled (
true), changing a password immediately revokes all other active sessions across all devices for that user account.
- When enabled (
9. Performance Monitoring (MetricsSettings)
- Native Prometheus Exposer: Built-in metrics engine listening on a dedicated port (default
:8067, e.g.http://localhost:8067/metrics). - Telemetry Coverage: Exposes hundreds of standard Prometheus metrics including HTTP request durations, database connection pool statistics, WebSocket connection counts, active Goroutines, memory allocations, CPU utilization, and WebSocket message dispatch rates.
- Client-Side Metrics: Enables collection of client render times, WebSocket round-trip ping latency, and interface responsiveness across connected browser clients.
10. Developer Settings (ServiceSettings)
- Internal Network Whitelist (
AllowedUntrustedInternalConnections):- Origin by Corvus blocks outbound requests to private and local network addresses by default to prevent Server-Side Request Forgery (SSRF).
- Administrators can whitelist internal subnets (e.g.
10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 127.0.0.1) and internal corporate domain names, enabling webhooks, slash commands, and integrations to securely communicate with intranet build servers, issue trackers, and internal APIs.
- Client Performance Debugging (
EnableClientPerformanceDebugging):- Allows individual team members or administrators to inspect real-time network and render performance statistics in their client settings under Settings > Advanced > Performance Debugging.
7. Master Operational Ceilings & Maximum Platform Limits
Origin by Corvus is engineered to provide maximum operational flexibility, high-throughput capability, and zero artificial software restrictions for on-premise and air-gapped corporate deployments. System Administrators can tune each subsystem to its absolute physical and architectural limits based on available server hardware and organizational requirements.
7.1 Master Limits & Operational Ceilings Matrix
The following matrix establishes the absolute highest limits, maximum parameters, and unconstrained ceilings across all functional areas of Origin by Corvus:
| Functional Category | Parameter / Configuration Key | Default Out-of-the-Box | Absolute Highest Possible Ceiling | Operational Impact & Guidance |
|---|---|---|---|---|
| Messaging & Content | Message Text Length (PostMessageMaxBytes) | 4,000 characters | 262,144 Characters (1 MB) | Up to 16,383 UTF-8 characters in V2 schema; up to 262,144 UTF-8 runes (1,048,576 bytes / 1 MB) in V3 schema. Eliminates truncation for large code snippets, logs, and technical briefs. |
| Messaging & Content | Post Props & Metadata (PostPropsMaxRunes) | 40,000 runes | 800,000 Runes (~800 KB) | High-capacity metadata buffer for bot integrations, interactive webhook buttons, embedded cards, and structured JSON payloads. |
| Messaging & Content | File Attachments Per Post (MaxFilesPerPost) | 10 files | 10 Files (Up to 40 GB Total per Post) | Up to 10 distinct files per post at 4 GB per file, allowing up to 40 GB of attachments delivered in a single message transmission. |
| Messaging & Content | Emoji Reactions Per Post (MaxUniqueReactionsPerPost) | 50 reactions | 500 Unique Emoji Reactions | Hard architectural ceiling on distinct emoji reaction types per message post (ServiceSettingsMaxUniqueReactionsPerPost = 500). |
| Messaging & Content | Message Retention & History | Indefinite Local Storage | Unlimited / 100% Lifetime Retention | Zero artificial message history limits (no 10,000-message lock, no 90-day archive cutoffs). All messages remain searchable in perpetuity. |
| Messaging & Content | Search Result Pagination (MaxReportingPerPage) | 100 posts/page | 1,000 Posts Per Page | Maximum number of posts retrieved per page in reporting, audit, and compliance search endpoints. |
| Collaboration & Teams | Team Workspace Member Capacity | 50 users | Up to 250 Concurrent Active Members | Sized for up to 250 simultaneously active connected members per team workspace on single-node hardware (supporting thousands of registered users). |
| Collaboration & Teams | Users Per Team (TeamSettings.MaxUsersPerTeam) | 50 users | Unlimited / Thousands | Configurable upper bound on total members that can join a single organizational team. |
| Collaboration & Teams | Channels Per Team Workspace | Unlimited | Unlimited Public & Private Channels | Zero artificial limits on channel creation. Teams can organize work across hundreds or thousands of channels. |
| Collaboration & Teams | Teams Per Platform Instance | Unlimited | Unlimited Organizational Teams | Multi-team architecture allowing multiple departments, business units, or project teams on a single instance. |
| Collaboration & Teams | Group Direct Messaging Limit (ChannelGroupMaxUsers) | 8 participants | 8 Simultaneous Participants | Group DM ceiling for ad-hoc private multi-party messaging. For larger groups, private channels provide unlimited membership. |
| Collaboration & Teams | Team Allowed Domains (TeamAllowedDomainsMaxLength) | 500 characters | 500 Characters | Maximum character length for whitelisting allowed corporate email domains during user self-registration. |
| Origin Calls (Audio/Video) | Voice & Screen Share Duration | Unlimited | Unlimited Continuous Duration (24/7) | Zero arbitrary time limits (no 45-minute or 60-minute cutoff). Calls can remain active indefinitely. |
| Origin Calls (Audio/Video) | Simultaneous Call Participants | Up to 8 users | 50 – 100 Simultaneous Participants | Governed by RTC server resources and network bandwidth. Supports team-wide standups, all-hands audio, and channel meetings. |
| Origin Calls (Audio/Video) | Screen Share Video Resolution | 1080p @ 15-30 FPS | 4K UHD (3840 Ã - 2160) @ up to 60 FPS | Adaptive WebRTC pipeline dynamically negotiates VP8/H.264 video streams at native display resolutions for ultra-crisp document and code reviews. |
| Origin Calls (Audio/Video) | Concurrent Channel Calls | Unlimited | Unlimited Concurrent Calls | Separate voice channels across teams and channels can run simultaneously without channel contention. |
| Origin Boards (Projects) | Cards / Tasks Per Board | Unlimited | Unlimited Cards & Tasks | Zero artificial caps on tasks, cards, notes, or backlog items across Kanban, Table, Calendar, and Gallery views. |
| Origin Boards (Projects) | Boards Per Channel / Workspace | Unlimited | Unlimited Project Boards | Every public channel, private channel, or user can maintain independent project boards. |
| Origin Boards (Projects) | Board Views & Custom Properties | Unlimited | Unlimited Views & Attributes | Complete flexibility to define custom card properties (select, multi-select, dates, URLs, numbers, person assignments). |
| Origin Workflows (Playbooks) | Concurrent Active Playbook Runs | Unlimited | Unlimited Active Workflow Runs | No licensing caps on concurrent incident responses, onboarding playbooks, or automated operational checklists. |
| Origin Workflows (Playbooks) | Workflow Steps & Checklist Items | Unlimited | Unlimited Stages & Tasks | Comprehensive multi-stage playbooks with automated webhooks, slash command triggers, and retrospective timelines. |
| File Storage & Media | Single File Upload Size (FileSettings.MaxFileSize) | 100 MB (104,857,600 B) | 4,294,967,296 Bytes (4 GB) | Maximum individual file attachment size. Supports massive dataset archives, virtual disk images, CAD models, and video recordings. |
| File Storage & Media | Image Preview Resolution (MaxImageResolution) | 33,177,600 Pixels (8K) | 100,000,000+ Pixels (~100 Megapixels) | Server-side image decoding ceiling for rendering inline thumbnails of architectural blueprints and panoramic photos. |
| File Storage & Media | Image Decoder Concurrency (MaxImageDecoderConcurrency) | -1 (Auto / All Cores) | Unlimited / All CPU Cores (-1) | Multi-threaded parallel image decompression across all physical and virtual CPU cores on the host. |
| File Storage & Media | S3 / MinIO Multipart Chunk Size | 5 MB (5,242,880 B) | 104,857,600 Bytes (100 MB) | Part size for S3 multipart streaming uploads, optimizing throughput on fast corporate networks. |
| File Storage & Media | Total Repository Storage Capacity | Bounded by disk | Unlimited Storage | Unconstrained by software licensing; bounded only by physical NVMe/SSD drive capacity or S3/MinIO bucket quotas. |
| Sessions & Access | Web Browser Session Length (SessionLengthWebInHours) | 720 hours (30 days) | 87,600 Hours (10 Full Years) | Maximum active session lifespan for desktop web browsers and PWAs using credentials or LDAP. |
| Sessions & Access | Mobile Web / PWA Session Length (SessionLengthMobileInHours) | 720 hours (30 days) | 87,600 Hours (10 Full Years) | Maximum session lifespan for mobile browser clients and installed PWAs. |
| Sessions & Access | SSO Session Length (SessionLengthSSOInHours) | 720 hours (30 days) | 87,600 Hours (10 Full Years) | Maximum session lifespan for corporate Single Sign-On (GitLab, SAML, OAuth 2.0). |
| Sessions & Access | Active Session RAM Cache (SessionCacheInMinutes) | 10 minutes | 1,440 Minutes (24 Hours) | Duration authenticated user session tokens remain cached in server RAM, minimizing database query loads. |
| Sessions & Access | Session Idle Timeout (SessionIdleTimeoutInMinutes) | 0 (Unlimited / Disabled) | 525,600 Minutes (1 Year) or 0 (Indefinite) | Set to 0 for indefinite continuous login while browser remains open; or configure up to 1 year idle threshold. |
| Sessions & Access | Session Renewal on Activity (ExtendSessionLengthWithActivity) | false | Enabled (true) | Every user interaction automatically resets session expiry, ensuring actively working team members are never logged out. |
| Sessions & Access | Personal Access Token Lifetime (MaximumPersonalAccessTokenLifetimeDays) | 365 days | 36,500 Days (100 Years) | Maximum validity period for programmatic bot and integration tokens (MaxPersonalAccessTokenLifetimeDays = 36500). |
| Sessions & Access | Password Character Limit (PasswordMaximumLength) | 72 characters | 72 Characters (Native) / Unlimited (LDAP/SAML) | Maximum bcrypt password string length. Corporate LDAP/SAML integrations support arbitrary lengths. |
| Sessions & Access | Failed Login Lockout Ceiling (MaximumLoginAttempts) | 10 attempts | 1,000 Attempts or Disabled (0) | Failed authentication attempts before account/IP lockout. Can be disabled (0) in secure private networks. |
| Database & Pooling | Maximum Open Database Connections (SqlSettings.MaxOpenConns) | 300 connections | 1,000 – 2,000+ Connections | Matched to PostgreSQL/MySQL max_connections for massive concurrent read/write query capacity. |
| Database & Pooling | Pre-Warmed Idle Connections (SqlSettings.MaxIdleConns) | 20 connections | 300 – 500 Connections | Maintains an active warm pool to eliminate TCP/TLS connection handshake overhead during traffic bursts. |
| Database & Pooling | Transactional Query Timeout (SqlSettings.QueryTimeout) | 30 seconds | 300 Seconds (5 Minutes) | Timeout ceiling for standard transactional database operations before aborting. |
| Database & Pooling | Analytics Query Timeout (SqlSettings.AnalyticsQueryTimeout) | 30 seconds | 600 Seconds (10 Minutes) | Timeout allowance for deep organization-wide statistical rollups and audit queries. |
| Database & Pooling | Schema Migration Timeout (SqlSettings.MigrationsStatementTimeoutSeconds) | 1,000 seconds | 7,200 Seconds (2 Hours) | Allowance for large database indexing and table schema migrations during system upgrades. |
| Database & Pooling | Connection Recycling Lifetime (ConnMaxLifetimeMilliseconds) | 3,600,000 ms (1 hr) | Unlimited (0) or 86,400,000 ms (24 hrs) | When set to 0, database pool connections stay alive indefinitely without reconnection overhead. |
| Network & Web Server | Maximum API / Webhook Payload (MaximumPayloadSizeBytes) | 300,000 Bytes (~300 KB) | 104,857,600 Bytes (100 MB) | Maximum size for incoming REST API and webhook JSON payloads, enabling heavy automated data ingestion. |
| Network & Web Server | Connection Read Timeout (ServiceSettings.ReadTimeout) | 300 seconds (5 min) | 3,600 Seconds (1 Hour) | Maximum time from connection accepted to request body read completion. |
| Network & Web Server | Connection Write Timeout (ServiceSettings.WriteTimeout) | 300 seconds (5 min) | 3,600 Seconds (1 Hour) | Maximum time from request processing to complete response delivery over high-latency links. |
| Network & Web Server | HSTS Strict Transport Security Max-Age | 63,072,000 s (2 years) | 315,360,000 Seconds (10 Years) | Enforces strict HTTPS transport security across client browsers for up to a decade. |
| Network & Web Server | URL String Length (ServiceSettingsDefaultMaxURLLength) | 2,048 characters | 2,048 Characters | Maximum allowed length for inbound and outbound HTTP URL strings. |
| Rate Limiting | In-Memory Key Tracking Pool (RateLimitSettings.MemoryStoreSize) | 10,000 keys | 500,000 Distinct Tracked Keys | Concurrent client IP addresses and user tokens tracked in RAM (~25-50 MB RAM total footprint). |
| Rate Limiting | Continuous Request Rate (RateLimitSettings.PerSec) | 10 requests/sec | 1,000+ Requests/Second | Maximum continuous sustained API requests allowed per second per tracked user or IP address. |
| Rate Limiting | Peak Burst Allowance (RateLimitSettings.MaxBurst) | 100 requests | 2,000 Burst Requests | Maximum burst request allowance beyond the steady-state per-second rate limit. |
| Logging & Auditing | Log File Rotation Size (LogSettings.MaxFileSizeMB) | 100 MB | 1,000 MB (1 GB) | Size threshold before automatic rotation into compressed gzip archives (origin.YYYY-MM-DD.001.gz). |
| Logging & Auditing | Diagnostic Verbosity Level | INFO | DEBUG (Full Tracing) | Deep diagnostic capture including complete SQL statement execution traces and webhook payloads. |
7.2 Detailed Ceilings by Functional Domain
1. Messaging, History & Rich Content
- Text Capacity: While standard workplace communication averages 150 characters, Origin by Corvus supports messages up to 262,144 UTF-8 characters (1 MB) in PostgreSQL installations with V3 message schemas. This allows full code repositories, stack traces, configuration templates, and legal briefs to be posted directly into channels without third-party pastebins.
- Attachment Bulk Delivery: Each post supports up to 10 distinct file attachments. With
MaxFileSizeconfigured to its 4 GB ceiling, a single message can transmit up to 40 GB of attachments. - Interactive Props & Metadata: The post metadata buffer accommodates up to 800,000 runes (~800 KB), allowing sophisticated bot automations to attach multi-button action cards, dropdown selections, interactive forms, and multi-tier embeds to a single message.
- Reactions: Up to 500 unique emoji reactions per post are supported, allowing large teams to conduct comprehensive polling and feedback directly on announcements.
- Message History: Retention is 100% indefinite by default. Origin by Corvus maintains complete conversational history in the local database. Users can search and retrieve messages sent years earlier with sub-second response times.
2. Workspaces, Teams & Scalability
- Concurrency Capacity: Sized to comfortably host up to 250 concurrently active collaborating users per team workspace on standard modern server hardware (4 vCPU, 8 GB RAM).
- Team & Channel Growth: Organizations can create unlimited teams (workspaces) and unlimited channels (public, private, and announcement-only). There are no licensing tier gates restricting team or channel counts.
- Group Direct Messaging: Up to 8 users can collaborate in an ad-hoc private group conversation (
ChannelGroupMaxUsers). When broader collaboration is needed, private channels support unlimited membership.
3. Origin Calls (Voice, Video & Screen Sharing)
- Session Duration: Calls have no artificial duration caps (unlike third-party platforms with 40-minute or 60-minute limits). A team call or screen-sharing session can run continuously 24 hours a day, 7 days a week.
- Meeting Attendance: Designed to comfortably accommodate up to 50 to 100 simultaneous participants per call on standard server hardware with adequate network egress bandwidth.
- Screen Sharing Fidelity: Supports full 4K UHD (3840 Ã - 2160) screen sharing at up to 60 FPS, utilizing hardware-accelerated VP8/H.264 video streams. Bandwidth adapts dynamically to each participant's network connection.
4. Origin Boards & Workflows
- Project Boards: Every team and channel can create an unlimited number of boards, each containing an unlimited number of cards/tasks.
- Views & Fields: Each board supports unlimited Kanban columns, Table spreadsheets, Calendar timelines, and Gallery cards, with custom property schemas (status, priority, dates, assignees, multi-select tags).
- Automated Workflows (Playbooks): No monthly run quotas or concurrency caps. Organizations can execute unlimited simultaneous incident response workflows, compliance audits, and new hire onboarding sequences.
5. File Storage & Media Processing
- Maximum File Attachment Ceiling: Supports individual files up to 4 GB (
4,294,967,296bytes). To enable this, configureclient_max_body_size 4096M;in Nginx and setFileSettings.MaxFileSize: 4294967296. - Ultra-High-Resolution Imaging: The image decoder ceiling of 100,000,000+ pixels (~100 MP) ensures that complex architectural CAD renderings, high-density satellite imagery, and panoramic photos generate inline thumbnails reliably without server out-of-memory errors.
- CPU Concurrency:
MaxImageDecoderConcurrency: -1leverages all host CPU cores simultaneously for instantaneous image rendering.
6. Sessions, Authentication & Security
- Ultra-Long Session Lifetimes: For corporate environments where repeated logins are friction-inducing, web and mobile session lengths can be set up to 87,600 hours (10 years). Combined with
ExtendSessionLengthWithActivity: true, active workstations maintain uninterrupted persistent access. - Personal Access Tokens (PAT): Machine-to-machine integrations and CI/CD bots can be issued access tokens valid for up to 36,500 days (100 years) (
MaxPersonalAccessTokenLifetimeDays = 36500). - RAM Session Cache: Authenticated user tokens are cached in server RAM for up to 1,440 minutes (24 hours), eliminating redundant database session lookups during high-volume API and WebSocket traffic.
- Idle Timeout Governance: When security policies mandate automatic logouts for unattended workstations,
SessionIdleTimeoutInMinutescan be calibrated from 5 minutes up to 525,600 minutes (1 year), or disabled (0) for continuous access.
7. Database & High-Throughput Pooling
- Connection Ceilings: On high-core database instances,
MaxOpenConnscan be configured up to 2,000+ andMaxIdleConnsup to 500, maintaining an always-ready pool capable of servicing thousands of concurrent database operations per second. - Query Timeouts: Standard transactional queries allow up to 300 seconds (5 minutes) and analytics rollups allow up to 600 seconds (10 minutes), ensuring deep queries across massive datasets complete reliably without timeouts.
8. Network, API & Rate Limiting
- API Ingestion: Inbound REST and webhook JSON payloads can be configured up to 100 MB (
104,857,600bytes) viaServiceSettings.MaximumPayloadSizeBytes, allowing automated bots to push large batches of documentation, log dumps, or database records in a single call. - Rate Limit Ceiling: Sustained API traffic can be tuned up to 1,000+ requests/second with 2,000 burst requests, backed by an in-memory tracking pool of up to 500,000 distinct IP/user keys (
RateLimitSettings.MemoryStoreSize). - Transport Security: Strict-Transport-Security (HSTS) headers can be enforced for up to 315,360,000 seconds (10 years).
8. Enterprise Deployment & Operations Manual (Step-by-Step Client Guide)
This section provides the complete, production-grade deployment and operations manual for system administrators, DevOps engineers, and IT teams deploying Origin by Corvus within corporate on-premise, private cloud, or air-gapped environments.
8.1 Architecture & Port Matrix
Origin by Corvus runs as an isolated micro-service stack managed via container orchestration. All components reside on the customer's server without outbound cloud telemetry.
Firewall & Port Allocation Matrix:
| Port | Protocol | Direction | Source / Destination | Purpose | Mandatory? |
|---|---|---|---|---|---|
| 80 | TCP | Inbound | Public / Corporate LAN | HTTP to HTTPS redirection and ACME Let's Encrypt SSL challenges. | Yes |
| 443 | TCP | Inbound | Public / Corporate LAN | HTTPS encrypted web client access and WebSocket persistent connections (wss://). | Yes |
| 8443 | UDP | Inbound | Public / Corporate LAN | Origin Calls WebRTC media streams (low-latency encrypted Opus audio and VP8 screen sharing). | Yes (for Calling) |
| 8443 | TCP | Inbound | Public / Corporate LAN | Origin Calls WebRTC media fallback for clients on UDP-blocked networks. | Optional |
| 587 / 465 | TCP | Outbound | Corporate SMTP Server | Outgoing email relay for invitations, password resets, and mention notifications. | Yes (for Email) |
| 3478 / 5349 | UDP/TCP | In/Out | STUN/TURN Server | WebRTC NAT traversal relay (coturn) for remote users behind symmetric corporate NATs. | Optional (WAN only) |
8.2 Pre-Deployment Server Preparation
Before running the installer or starting containers, prepare the host operating system and networking:
Step 1: Provision Server Hardware / VM
Ensure the host meets the sizing criteria in Section 2.2:
- Small Deployments (1 – 100 members): 2 vCPUs, 4 GB RAM, 50 GB SSD.
- Standard Deployments (100 – 250 members): 4 vCPUs, 8 GB RAM, 150 GB SSD.
- Operating System: Ubuntu 22.04 LTS / 24.04 LTS, Debian 12, RHEL 9 / Rocky Linux 9, or Windows Server 2022.
Step 2: Configure Public or Intranet DNS
Create a DNS A Record pointing your chosen Fully Qualified Domain Name (FQDN) to your server's static IP address:
Type: A
Name: origin.yourcompany.com (or chat.yourcompany.com)
Value: 203.0.113.10 (Your Server Static Public or Intranet IP)
TTL: 300 seconds (5 minutes)
Step 3: Configure Host Firewalls
For Ubuntu / Debian (ufw):
# Allow SSH access
sudo ufw allow 22/tcp
# Allow Web & WebSocket Traffic
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
# Allow WebRTC Voice & Screen Sharing Media
sudo ufw allow 8443/udp
sudo ufw allow 8443/tcp
# Enable firewall
sudo ufw enable
sudo ufw status
For RHEL / Rocky Linux (firewalld):
sudo firewall-cmd --permanent --add-service=ssh
sudo firewall-cmd --permanent --add-service=http
sudo firewall-cmd --permanent --add-service=https
sudo firewall-cmd --permanent --add-port=8443/udp
sudo firewall-cmd --permanent --add-port=8443/tcp
sudo firewall-cmd --reload
For Windows Server (PowerShell Administrator):
New-NetFirewallRule -DisplayName "Origin-HTTP" -Direction Inbound -LocalPort 80 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Origin-HTTPS" -Direction Inbound -LocalPort 443 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Origin-Calls-UDP" -Direction Inbound -LocalPort 8443 -Protocol UDP -Action Allow
New-NetFirewallRule -DisplayName "Origin-Calls-TCP" -Direction Inbound -LocalPort 8443 -Protocol TCP -Action Allow
Step 4: Verify Host Resources
Confirm memory and disk availability:
# Verify available RAM (minimum 4 GB)
free -h
# Verify available SSD storage (minimum 50 GB root/mount)
df -h /
8.3 Delivery Artifacts & Integrity Verification
Quantum Tiger delivers Origin by Corvus to enterprise clients as compiled release packages and automated installers without exposing proprietary source code. The client receives:
- Automated Installers (located in the repository root):
install.sh(Linux/macOS) —https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus/raw/main/install.shinstall.ps1(Windows) —https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus/raw/main/install.ps1
- Private Registry Credentials: Gitea PAT with
read:repository+read:packagesscopes.
Verify Delivery Checksums:
Verify file integrity before execution:
# On Linux / macOS (after downloading installer):
sha256sum install.sh
# On Windows (PowerShell):
Get-FileHash -Algorithm SHA256 .\install.ps1
Compare the resulting hash against the release signature provided in your delivery certificate.
8.4 Deployment Method A: Single-Command Automated Installer (Recommended)
The automated installer provides the simplest installation experience — a single command that handles everything:
- Prompts once for your Gitea PAT and authenticates with the private container registry
- Configures the entire stack — Docker Engine, PostgreSQL 15, MinIO S3, Nginx reverse proxy, automatic SSL certificates, secure credentials, scheduled backup jobs
- Completes in under 5 minutes
Linux / macOS (Single Command):
curl -fsSL https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus/raw/main/install.sh | sudo bash
Windows (PowerShell as Administrator):
irm https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus/raw/main/install.ps1 | iex
What the Installer Does Automatically:
- Prompts for one Gitea PAT (with
read:repository+read:packagesscopes) - Authenticates with private Gitea container registry
- Runs full installation (Docker, PostgreSQL, MinIO, Nginx, SSL, backups)
- Displays final URL and management commands
Manual Installer (Alternative)
If you prefer to run the installer directly:
# Linux/macOS
curl -fsSL https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus/raw/main/install.sh -o install.sh
chmod +x install.sh
sudo ./install.sh
# Windows (PowerShell Admin)
irm https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus/raw/main/install.ps1 -OutFile install.ps1
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\install.ps1 install
The manual installer will prompt for the Gitea PAT during installation if not provided via GITEA_PAT environment variable.
8.5 Deployment Method B: Manual Production Docker Compose Deployment
For DevOps teams with strict Infrastructure-as-Code (IaC) governance or custom orchestration pipelines, you can deploy manually using standard Docker Compose.
Step 1: Create Directory Structure
sudo mkdir -p /opt/origin/certbot/conf /opt/origin/certbot/www /opt/origin/backups
cd /opt/origin
Step 2: Create Environment Secrets File (.env)
Create /opt/origin/.env and lock permissions (chmod 600 .env):
# Origin by Corvus — Production Environment Configuration
DOMAIN=origin.yourcompany.com
ADMIN_EMAIL=admin@yourcompany.com
# Auto-Generated Cryptographic Secrets (Generate via: openssl rand -hex 24)
DB_PASSWORD=9a4f2c81d7e35b08a6c1e9f42d7b8a3e1c5f0d9a6b2e4c8f
MINIO_USER=origin_storage_admin
MINIO_PASSWORD=3e8b1d9c7a5f0e2b4d6a8c1f3e5b7d9a2c4e6f8a0b1d3e5f
JWT_SECRET=f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2
Step 3: Create docker-compose.yml
Save the following configuration as /opt/origin/docker-compose.yml:
version: '3.8'
networks:
origin-net:
driver: bridge
volumes:
postgres_data:
minio_data:
origin_data:
origin_logs:
origin_config:
origin_plugins:
services:
postgres:
image: postgres:15-alpine
container_name: origin-postgres
restart: always
environment:
POSTGRES_USER: origin_user
POSTGRES_PASSWORD: ${DB_PASSWORD}
POSTGRES_DB: origin_db
volumes:
- postgres_data:/var/lib/postgresql/data
networks:
- origin-net
healthcheck:
test: ["CMD-SHELL", "pg_isready -U origin_user -d origin_db"]
interval: 10s
timeout: 5s
retries: 5
minio:
image: minio/minio:latest
container_name: origin-minio
restart: always
command: server /data --console-address ":9001"
environment:
MINIO_ROOT_USER: ${MINIO_USER}
MINIO_ROOT_PASSWORD: ${MINIO_PASSWORD}
volumes:
- minio_data:/data
networks:
- origin-net
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
interval: 15s
timeout: 5s
retries: 3
minio-init:
image: minio/mc:latest
container_name: origin-minio-init
depends_on:
minio:
condition: service_healthy
networks:
- origin-net
entrypoint: >
/bin/sh -c "
until (/usr/bin/mc config host add minio http://minio:9000 ${MINIO_USER} ${MINIO_PASSWORD}) do sleep 2; done;
/usr/bin/mc mb minio/origin-files --ignore-existing;
/usr/bin/mc anonymous set download minio/origin-files;
exit 0;
"
origin:
image: origin-corvus:local
container_name: origin-app
restart: always
depends_on:
postgres:
condition: service_healthy
minio:
condition: service_healthy
networks:
- origin-net
ports:
- "8443:8443/udp" # WebRTC Audio & Screen Share media
- "8443:8443/tcp" # WebRTC Media TCP fallback
expose:
- "8065" # HTTP & WebSocket (routed via Nginx)
environment:
# Database Connection
MM_SQLSETTINGS_DRIVERNAME: postgres
MM_SQLSETTINGS_DATASOURCE: "postgres://origin_user:${DB_PASSWORD}@postgres:5432/origin_db?sslmode=disable&connect_timeout=10"
# S3 Object Storage (MinIO)
MM_FILESETTINGS_DRIVERNAME: amazons3
MM_FILESETTINGS_AMAZONS3ACCESSKEYID: ${MINIO_USER}
MM_FILESETTINGS_AMAZONS3SECRETACCESSKEY: ${MINIO_PASSWORD}
MM_FILESETTINGS_AMAZONS3BUCKET: origin-files
MM_FILESETTINGS_AMAZONS3ENDPOINT: minio:9000
MM_FILESETTINGS_AMAZONS3SSL: "false"
MM_FILESETTINGS_AMAZONS3REGION: "auto"
MM_FILESETTINGS_MAXFILESIZE: "4294967296" # 4 GB
# Site URL & Network Security
MM_SERVICESETTINGS_SITEURL: "https://${DOMAIN}"
MM_SERVICESETTINGS_ENABLELOCALMODE: "true"
MM_SERVICESETTINGS_TLSSTRICT: "true"
MM_SERVICESETTINGS_FORWARD80TO443: "true"
MM_SERVICESETTINGS_ENABLECLIENTPERFORMANCEDEBUGGING: "true"
# Logging
MM_LOGSETTINGS_ENABLECONSOLE: "true"
MM_LOGSETTINGS_CONSOLELEVEL: "INFO"
MM_LOGSETTINGS_CONSOLEJSON: "true"
MM_LOGSETTINGS_ENABLEFILE: "true"
MM_LOGSETTINGS_FILELEVEL: "INFO"
MM_LOGSETTINGS_FILEJSON: "true"
# Email Notifications
MM_EMAILSETTINGS_ENABLE: "true"
MM_EMAILSETTINGS_FEEDBACKNAME: "Origin by Corvus"
MM_EMAILSETTINGS_FEEDBACKEMAIL: "${ADMIN_EMAIL}"
volumes:
- origin_data:/origin/data
- origin_logs:/origin/logs
- origin_config:/origin/config
- origin_plugins:/origin/plugins
nginx:
image: nginx:alpine
container_name: origin-nginx
restart: always
depends_on:
- origin
networks:
- origin-net
ports:
- "80:80"
- "443:443"
volumes:
- ./nginx.conf:/etc/nginx/nginx.conf:ro
- ./certbot/conf:/etc/letsencrypt:ro
- ./certbot/www:/var/www/certbot:ro
certbot:
image: certbot/certbot:latest
container_name: origin-certbot
restart: unless-stopped
volumes:
- ./certbot/conf:/etc/letsencrypt:rw
- ./certbot/www:/var/www/certbot:rw
entrypoint: "/bin/sh -c 'trap exit TERM; while :; do certbot renew; sleep 12h & wait $${!}; done;'"
Step 4: Create nginx.conf
Save the following configuration as /opt/origin/nginx.conf:
events {
worker_connections 2048;
}
http {
include /etc/nginx/mime.types;
default_type application/octet-stream;
# Performance Optimizations
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
# GZIP Compression
gzip on;
gzip_vary on;
gzip_proxied any;
gzip_comp_level 6;
gzip_types text/plain text/css text/xml application/json application/javascript application/xml+rss text/javascript image/svg+xml;
# Large File Upload Capacity (4 GB)
client_max_body_size 4096M;
# WebSocket Upgrade Mapping
map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
# Upstream Backend Pool
upstream origin_backend {
server origin:8065;
keepalive 32;
}
# HTTP Server (Redirect to HTTPS & ACME Challenge)
server {
listen 80;
server_name _;
location /.well-known/acme-challenge/ {
root /var/www/certbot;
}
location / {
return 301 https://$host$request_uri;
}
}
# HTTPS Server (SSL Termination & WebSocket Proxy)
server {
listen 443 ssl http2;
server_name _;
# SSL Certificates (Let's Encrypt or Custom Organizational Certificates)
ssl_certificate /etc/letsencrypt/live/origin.yourcompany.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/origin.yourcompany.com/privkey.pem;
# Modern TLS Security Parameters
ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers off;
ssl_ciphers "ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384";
ssl_session_cache shared:SSL:10m;
ssl_session_timeout 1d;
ssl_session_tickets off;
# Security Headers
add_header X-Frame-Options "SAMEORIGIN" always;
add_header X-XSS-Protection "1; mode=block" always;
add_header X-Content-Type-Options "nosniff" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload" always;
# Proxy Headers
proxy_http_version 1.1;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Frame-Options SAMEORIGIN;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
# Extended Timeouts for Large Uploads & Real-Time Sync
proxy_connect_timeout 300s;
proxy_send_timeout 3600s;
proxy_read_timeout 3600s;
proxy_buffers 16 128k;
proxy_buffer_size 256k;
location / {
proxy_pass http://origin_backend;
}
}
}
Step 5: Start the Container Stack
# Load offline tarball (if using tarball delivery)
docker load -i origin-corvus.tar
# Launch all containers in detached mode
docker compose up -d
# Verify container operational status
docker compose ps
8.6 Post-Deployment Initial Setup & Configuration Checklist
Once all containers report healthy status (docker compose ps), complete the 6-step initialization wizard via your web browser:
Step 1: Access the Instance
Open your browser and navigate to:
https://origin.yourcompany.com
Step 2: Create Primary System Administrator Account
The initial setup wizard automatically appears on first launch:
- Admin Name: Enter your full name.
- Username: Choose an administrative username (e.g.,
sysadmin). - Email Address: Enter your corporate email (receives administrative security alerts).
- Password: Set a strong password (minimum 12 characters recommended).
- Organization / Team Workspace Name: Enter your company or project name (e.g.,
Quantum Engineering). - Click Create Account.
Step 3: Configure Corporate SMTP Mail Relay
To enable team invitations, user onboarding emails, and password resets:
- Open the Product Switcher (9-dot menu in top-left) $\rightarrow$ System Console.
- In the left navigation, navigate to Environment > SMTP.
- Configure your corporate mail parameters:
- SMTP Server:
mail.yourcompany.com(orsmtp.sendgrid.net,email-smtp.us-east-1.amazonaws.com). - SMTP Port:
587(forSTARTTLS) or465(forTLS). - Connection Security: Select
STARTTLSorTLS. - SMTP Username & Password: Enter credentials for your mail account.
- Feedback Name:
Origin Notifications. - Feedback Email:
no-reply@yourcompany.com.
- SMTP Server:
- Click Save, then click Test Connection to verify mail dispatch.
Step 4: Verify Origin Calls (WebRTC Voice & Screen Sharing)
- In System Console, navigate to Plugins > Origin Calls.
- Verify that Enable Plugin is set to
true. - Default Port: Verify UDP Port
8443is set. - STUN/TURN Configuration (For Remote WAN users):
- If employees join calls across the public internet from behind strict NATs, enter your self-hosted coturn server details:
- STUN Server:
stun:turn.yourcompany.com:3478 - TURN Server:
turn:turn.yourcompany.com:3478 - TURN Username & Shared Secret: Enter your coturn auth secret.
- STUN Server:
- If employees join calls across the public internet from behind strict NATs, enter your self-hosted coturn server details:
- Click Save.
Step 5: Verify S3 File Storage
- In System Console, navigate to Environment > File Storage.
- Verify File Storage Driver is set to
Amazon S3. - Confirm bucket name is
origin-filesand endpoint isminio:9000. - Set Maximum File Size to
4294967296(4 GB) or your preferred organizational cap. - Click Save.
Step 6: Configure Security & Authentication Policies
- In System Console, navigate to Authentication > Multi-Factor Authentication:
- Set Enable Multi-Factor Authentication to
trueto allow TOTP authenticator apps (Google Authenticator, Microsoft Authenticator, 1Password).
- Set Enable Multi-Factor Authentication to
- Navigate to Environment > Session Lengths:
- Set Session Length Web (Hours) to
8760(1 year) to maintain persistent desktop sessions. - Ensure Extend Session Length with Activity is set to
true.
- Set Session Length Web (Hours) to
- Click Save.
8.7 Client Access, PWA Installation & Team Onboarding
Origin by Corvus requires zero client software distribution. Employees access the platform via any modern web browser or as a standalone desktop/mobile app via Progressive Web App (PWA) technology.
Desktop Access & App Installation:
- Open
https://origin.yourcompany.comin Google Chrome, Microsoft Edge, or Mozilla Firefox. - To install as a desktop windowed application:
- In Google Chrome / Brave: Click the Install App icon in the address bar (or Menu $\rightarrow$ Install Origin by Corvus).
- In Microsoft Edge: Click the App Available button in the address bar $\rightarrow$ Install.
- Origin by Corvus launches as a native desktop application with taskbar pinning, desktop shortcuts, and full OS window management.
- When prompted by the browser, click Allow for Notifications to receive instant desktop alerts.
Mobile Device Access & App Installation:
- Apple iOS (iPhone / iPad):
- Open Safari and navigate to
https://origin.yourcompany.com. - Tap the Share button (box with upward arrow) at the bottom of the screen.
- Scroll down and tap Add to Home Screen.
- Tap Add. Origin by Corvus appears on the home screen as a standalone app icon with full-screen view.
- Open Safari and navigate to
- Android Devices:
- Open Chrome and navigate to
https://origin.yourcompany.com. - Tap the three-dot menu $\rightarrow$ Install app (or Add to Home screen).
- Tap Install.
- Open Chrome and navigate to
Inviting Team Members:
- Inside Origin by Corvus, click the + icon beside direct messages or click the team menu $\rightarrow$ Invite People.
- Choose from:
- Shareable Invitation Link: Send the internal link via organizational email or intranet.
- Direct Email Invitations: Enter employee email addresses to automatically send onboarding invites via your configured SMTP server.
8.8 Post-Installation Operations & Full-Lifecycle Management (The 5 Operational Layers)
After running the initial installation, clients do not need to memorize disparate tools or write custom scripts. The installer itself (install.sh on Linux/macOS and install.ps1 on Windows) serves as a persistent, full-lifecycle operations CLI.
Post-installation operational activities can be performed through five distinct management layers:
Layer 1: Unified Operations CLI (install.sh / install.ps1)
The client can navigate to their deployment directory and execute operations either interactively or via headless command-line subcommands.
A. Interactive Operations Menu
Running the script without arguments opens an interactive terminal menu:
- Linux & macOS:
sudo ./install.sh
- Windows Server / Desktop (PowerShell Administrator):
.\install.ps1
Interactive Menu Options:
====================================================================
Origin by Corvus - Operations & Deployment CLI
Quantum Tiger (Morning Bay Technology Pvt. Ltd.)
====================================================================
Please choose an action:
1) Install Origin by Corvus (Production Stack)
2) Run preflight diagnostics
3) Verify cryptographic checksums
4) Update to a new version
5) Rollback to previous version
6) Check deployment status & health
7) Create manual backup
8) Uninstall Origin by Corvus
9) Exit
B. Direct Headless Subcommands
For automated administration, scheduled jobs, or terminal scripts:
| Operational Activity | Linux & macOS Command | Windows PowerShell Command | Description |
|---|---|---|---|
| Check Status & Health | sudo ./install.sh status | .\install.ps1 status | Probes container states, exposed ports, and the /api/v4/system/ping health endpoint. |
| Run Diagnostics | sudo ./install.sh diagnostics | .\install.ps1 diagnostics | Validates CPU, RAM, disk space, Docker engine, Compose plugin, and firewall ports. |
| Verify Checksums | sudo ./install.sh verify | .\install.ps1 verify | Validates all installer scripts against SHA-256 signatures in checksums.sha256. |
| Update Version | sudo ./install.sh update v1.1.0 | .\install.ps1 update v1.1.0 | Automates database pre-backup, pulls image from Gitea registry, restarts stack, and auto-rolls back if health check fails. |
| Rollback Version | sudo ./install.sh rollback | .\install.ps1 rollback | Instantly restores the previous container image and configuration backup. |
| Manual Backup | sudo ./install.sh backup | .\install.ps1 backup | Dumps PostgreSQL database (pg_dump) and compresses all persistent volumes into backups/. |
| Safe Uninstall | sudo ./install.sh uninstall | .\install.ps1 uninstall | Safely stops containers, archives configuration, and offers to preserve or wipe data. |
| Help Screen | sudo ./install.sh help | .\install.ps1 help | Displays the command syntax and usage parameters. |
Layer 2: Dedicated Convenience Commands (Linux PATH)
During installation on Linux, dedicated helper scripts are installed directly into /usr/local/bin/ so administrators can run them from any directory:
- Check Service Health:
origin-status
- Create Timestamped Backup:
Creates both a gzipped PostgreSQL dump (origin-backup
backups/manual-db-TIMESTAMP.sql.gz) and a full volume archive. - Apply Version Update:
origin-update v1.1.0
- Emergency Rollback:
origin-rollback
Automated Daily Backups:
The installer configures /etc/cron.d/origin-backup automatically on Linux:
- Daily at 2:00 AM: Full database dump (
backups/db_YYYY-MM-DD.sql.gz). - Weekly on Sundays at 3:00 AM: Full persistent volume backup (
backups/volumes_YYYY-MM-DD.tar.gz). - Daily at 4:00 AM: Automatic retention cleanup deleting backups older than 30 days.
Layer 3: Direct Docker Compose Management
Because Origin by Corvus is deployed via standard Docker Compose, administrators can also use standard Docker commands:
- Stream Live Container Logs:
# All servicesdocker compose logs -f# Application server onlydocker compose logs -f origin# Database logs onlydocker compose logs -f origin-postgres# Reverse proxy / SSL ingress logsdocker compose logs -f origin-nginx
- Restart Services (Controlled Restart):
# Restart only the application container without touching the databasedocker compose restart origin# Restart the full stackdocker compose restart
- Stop and Start the Deployment:
# Stop services without deleting datadocker compose down# Start services in the backgrounddocker compose up -d
Layer 4: In-Container CLI Management (mmctl)
For command-line user management, team setup, and system configuration:
- User Administration:
# List all registered usersdocker exec -it origin mmctl --local user list# Create a new team memberdocker exec -it origin mmctl --local user create --email user@company.com --username john --password "SecurePassword123"# Reset a forgotten passworddocker exec -it origin mmctl --local user reset-password john --password "NewPassword456"# Promote user to System Administratordocker exec -it origin mmctl --local user make-admin john
- Team & Channel Administration:
# List all teamsdocker exec -it origin mmctl --local team list# List channels in a teamdocker exec -it origin mmctl --local channel list <team-name>
- Direct Database Access:
docker exec -it origin-postgres psql -U origin_user -d origin_db
Layer 5: Web-Based Management (System Console)
For non-terminal administration, 100% of day-to-day operations can be managed graphically:
- Log in to
https://your-domain.comas a System Administrator. - Click the application grid icon in the top left and select System Console.
- Manage settings visually:
- Email / SMTP: Configure outbound email notifications.
- Origin Calls (WebRTC): Configure audio/video calling, WebRTC listening port (
8443), and STUN/TURN credentials. - Origin Boards & Playbooks: Configure project boards and workflow automation.
- Security & Authentication: Enforce Multi-Factor Authentication (MFA), password complexity, and session timeouts.
- Compliance & Exports: Generate audit logs and data exports.
Server Health Monitoring & Centralized Telemetry:
Integrate Origin by Corvus with your centralized monitoring tools (Nagios, Zabbix, Datadog, Prometheus):
- Healthcheck Endpoint:
HTTP GET https://origin.yourcompany.com/api/v4/system/pingreturns{"status":"OK"}with status code200. - Prometheus Metrics: Configure Prometheus to scrape
:8067/metricsfor live metrics on active WebSocket connections, CPU/memory consumption, and database latency.
8.9 Enterprise Backup Strategy & Disaster Recovery
Automated Daily Backup Schedule:
The universal installer configures automated daily backups:
- Daily Database Snapshots: Executed every night at
02:00 AMlocal server time, storing compressed.sql.gzarchives in/opt/origin/backups/. - Weekly Volume Archives: Executed every Sunday at
03:00 AMlocal server time, creating encrypted tarballs of user uploads. - Retention Policy: Backups older than 30 days are automatically pruned to prevent disk exhaustion.
Executing an Immediate On-Demand Backup:
Run a manual snapshot prior to system updates or host maintenance:
# Export compressed PostgreSQL database dump
docker exec origin-postgres pg_dump -U origin_user origin_db | gzip > /opt/origin/backups/manual_backup_$(date +%Y%m%d_%H%M%S).sql.gz
# Verify backup file size
ls -lh /opt/origin/backups/
Step-by-Step Disaster Recovery & Database Restoration:
In the event of server corruption or data recovery requirements, restore your database using the following sequence:
# 1. Stop the application server to prevent incoming database writes
docker compose stop origin
# 2. Drop existing database connections and recreate the clean database
docker exec -i origin-postgres psql -U origin_user -d postgres -c "SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE datname = 'origin_db' AND pid <> pg_backend_pid();"
docker exec -i origin-postgres psql -U origin_user -d postgres -c "DROP DATABASE origin_db;"
docker exec -i origin-postgres psql -U origin_user -d postgres -c "CREATE DATABASE origin_db OWNER origin_user ENCODING 'UTF8';"
# 3. Stream and restore the compressed SQL backup
gunzip -c /opt/origin/backups/origin_backup_20261107.sql.gz | docker exec -i origin-postgres psql -U origin_user -d origin_db
# 4. Restart the application container
docker compose up -d origin
# 5. Verify service health and data integrity
docker compose logs -f origin
8.10 Zero-Downtime Image Updates & Rollback
Using the Bundled Update Utility:
Origin by Corvus includes an update script that backs up configuration, loads the new image, updates Compose, and tests health before finalizing:
On Linux / macOS:
# Update from a new release tarball
sudo ./origin-update /path/to/origin-corvus-v1.2.tar
# Or update from your private registry tag
sudo ./origin-update v1.2
On Windows Server:
.\origin-update.ps1 -Source ".\origin-corvus-v1.2.tar"
Automatic Rollback Protection:
The update script monitors /api/v4/system/ping for 60 seconds after launching the new image. If the health check fails, it automatically reverts docker-compose.yml to the previous image tag and restarts the healthy container, guaranteeing business continuity.
8.11 Enterprise Troubleshooting & Verification Guide
| Issue / Symptom | Probable Root Cause | Resolution Command / Action |
|---|---|---|
| "Bad Gateway" / 502 Error | Application container starting up or crashed. | Check app logs: docker compose logs origin. Ensure PostgreSQL reports healthy (docker compose ps). |
| SSL Certificate Error on First Visit | Let's Encrypt rate-limited or port 80 blocked. | Ensure DNS A record resolves to public IP. Verify port 80 is reachable from the internet for ACME challenge. |
| "WebSocket Connection Failed" | Reverse proxy stripped WebSocket headers. | Verify nginx.conf contains proxy_set_header Upgrade $http_upgrade; and Connection $connection_upgrade;. |
| Voice Call Connects but No Audio | Host firewall blocking WebRTC UDP media port. | Open UDP Port 8443: sudo ufw allow 8443/udp. If users connect across strict corporate WANs, configure coturn STUN/TURN in System Console. |
| File Upload Fails with 413 Error | Nginx request body ceiling smaller than upload. | Add client_max_body_size 4096M; to your Nginx http or server block and reload Nginx (docker compose restart nginx). |
| Database Max Connections Reached | High concurrent load exceeding connection pool. | In System Console > Environment > Database, increase MaxOpenConns to 1000 and restart the stack. |
| SMTP Delivery Failure | Incorrect port, firewall blocking outbound, or wrong TLS mode. | Port 587 requires STARTTLS; Port 465 requires TLS. Verify outbound traffic on your server: nc -zv mail.yourcompany.com 587. |
| High Memory Consumption | Uncapped image caching or debug logging. | Set LogSettings.FileLevel to INFO. Ensure ServiceSettings.SessionCacheInMinutes is within 10 to 60 minutes. |
9. Technical Support & Enterprise SLA
For enterprise technical assistance, architecture reviews, license key renewals, or deployment verification:
- Engineering Organization: Quantum Tiger (Morning Bay Technology Pvt. Ltd.)
- Official Enterprise Portal: https://quantumtiger.in
- Technical Support Desk: support@quantumtiger.in
- Architecture Inquiries: contact@quantumtiger.in
© 2025 - present Origin by Corvus • Quantum Tiger (Morning Bay Technology Pvt. Ltd.). All rights reserved. Self-hosted sovereign collaboration software.