Loading...
Core, Trader and every strategy add-on have their own release-specific manual, practice tutorial, captioned supporting videos and downloadable PDF.
Browse all eight product guides →Cival Systems · Video library
3:46 · Source edition · narrated tutorial
Source-edition lesson for the September 28 release. Demo imagery is illustrative and can show a broader dashboard than the purchased archive. Use the product manual for exact installation requirements. Hosting, third-party services and trading funds are separate. No returns are promised.
Cival Systems · Video library
Choose a lesson below. These guided screenshots show a testnet workspace, not a completed mainnet setup.
2:16 · Hosted dashboard · testnet recording
Guided screenshots recorded on testnet, October 20, 2026. No wallet signing, transfer, strategy installation or activation was completed on camera. Your current workspace and official venue determine the network and available actions. Never send real funds to a testnet route.
01
Core includes the Darvas strategy. Trader includes Core and all six strategy frameworks. Add-ons need a compatible installed edition; they are not standalone dashboards. A source license does not include a cloud server, exchange funds or third-party API credits.
02
Sign in and verify your email before checkout. Keep the same account for payment and downloads. Review the cart, license, refund terms and add-on requirement. The server checks current availability and price before opening Stripe checkout.
03
A successful payment return page is followed by server-side payment verification. Check your account for the order and download action. If payment is processing, do not buy again. Send support the order reference if access does not arrive. Never send your wallet seed phrase or API secrets.
04
Open Account, locate the paid order and choose Download. Links expire; generate a fresh one from the account instead of reusing an old email link. Keep the ZIP, receipt, version and original checksum together. Extract into a new directory, not over a running installation.
The version in the downloaded package is authoritative. Do not use Core 2.0 demo instructions to install a 2.1 source edition.
These archives include a Next.js application, Supabase integration and strategy plugins. They need a Node environment compatible with package.json, a Supabase project with Auth and REST services, a PostgreSQL client for schema setup, and private server configuration. A plain PostgreSQL database is insufficient.
Release status: the September 28 source release passes clean Windows Core and Linux Trader installation, strict types, builds and strategy-loader checks. It supplies editable UI and frameworks. Full venue and recovery validation is still required before unattended or real-money operation.
PowerShell
psql "$env:DATABASE_URL" -v ON_ERROR_STOP=1 -f schema/001_core.sqlLinux / macOS
psql "$DATABASE_URL" -v ON_ERROR_STOP=1 -f schema/001_core.sqlThis is the separate paper-only template, with browser-local workspace storage. Its package declares Node 22.x. It does not connect to an exchange or accept funds. Do not mistake its demo for the 2.1 source edition.
npm ci
npm run check
npm run devOpen localhost:3000. Use the Paper Desk to submit a simulated order, inspect the audit log, and export a workspace backup from Settings. Hosted mode requires a matching Cival tenant configuration; leave it off for a local installation.
Funding, withdrawals and key approval have real effects on the selected network. Review wallet prompts and never send funds to a software product download or a support contact.
Open hosting setupAn add-on is a strategy module, not a complete app. Check the included manifest compatibility and INSTALL.md against your installed edition. Core already contains Darvas; Trader includes all six frameworks.
Complete this for each installation and major update. Keep the evidence with your release backup.
For self-hosting, keep the application behind HTTPS and authenticated access, bind internal services privately, and monitor uptime, data freshness, failed orders, disk space and database backups. Store encrypted backups separately from the server. Test restores. Before upgrading, preserve the old ZIP, lockfile, configuration and database snapshot; read migration notes and test the new version in isolation. Do not run two independent trading engines against the same account during a migration.
If rollback is needed, stop the new runtime, reconcile exchange orders and positions, and restore only a database version compatible with the chosen application. Restoring a database never reverses an exchange trade.
Sign in to the purchasing account and generate a new Download link. Expired links do not mean you need to purchase again.
Check the order status in Account. If pending, allow payment verification to finish. Contact support with the order reference and timestamp; do not retry payment to fix fulfillment.
You are probably running a 2.1 source edition. Configure a working Supabase project and the required server environment before building. Plain PostgreSQL alone does not provide the Auth and REST endpoints the app imports.
Some historical 2.1 archives did not include a lockfile. Use npm install only for that archive, preserve the generated package-lock.json, and inspect the resulting dependency/build errors. This is not evidence of a verified release.
Check manifest.json, entryPoint and the directory nesting: plugins/<plugin>/manifest.json and its compiled dist entry must exist. Read the loader errors after restart. Do not nest the complete ZIP inside another plugin directory.
Read the latest decision, data timestamp, configured symbol, account/network and risk rejection. Capital availability alone is not an entry signal. Confirm that an existing position is not already using the strategy’s position slot.
Match the account address and testnet/mainnet selection with the exchange. Refresh data and compare positions, fills and open orders. Do not duplicate an order while reconciliation is uncertain.
Stop installation at that step and retain the exact error and product version. Ask support for a corrected release. Do not turn off authentication, type checking or execution safeguards to work around it.
Include the order reference, product and version, operating system, Node version, failed step and a redacted error. Never include .env files, passwords, session tokens, seed phrases or private keys.