Run your own Dialogexa trial · 0.1.0

Run your own Dialogexa trial

Release: 0.1.0 test edition. Prepared October 1, 2026. This guide describes the software available in the trial download. The broader product vision on the website extends beyond this build.

Bring up a workspace of your own and explore customer messages, intake forms, internal guidance, direct replies, conversation takeover, reviewed drafts, and knowledge review. AI-generated replies, automatic translation, document processing, mobile push notifications, and a native iOS app are planned capabilities.

Pick the right download

Download	Best for	Included
Linux ARM64 trial	Technical users with a compatible ARM64 Linux server	Backend, bundled .NET runtime, SQLite components, and built web interfaces
Full source	Teams that want to inspect, adapt, or rebuild the project	Separate Visual Studio and Android Studio projects, web source, and the API contract

The prebuilt server targets linux-arm64. It has run on an aarch64 HolmesBox; other ARM64 Linux distributions have not been individually tested. For Windows, Linux x64, or macOS, build from source for your platform. The ARM64 Linux download cannot run directly on those systems.

The server package includes the .NET runtime, but your Linux system still needs the runtime's native dependencies. Check your architecture and Microsoft's guidance for your distribution before starting.

Start a private ARM64 Linux trial

Run these commands on your own test machine. The trial does not need a GPU. If the download carries a newer version suffix, use the filename shown on the download page.

Confirm the architecture:

uname -m

The result should be aarch64. Place the downloaded archive in your working directory. Compare its SHA-256 digest with the published download manifest, then inspect its contents:

sha256sum dialogexa-evaluation-linux-arm64.tar.gz
tar -tzf dialogexa-evaluation-linux-arm64.tar.gz

Keep the application and persistent data in separate directories. The data directory must stay outside wwwroot:

trial_root="$HOME/dialogexa-trial"
mkdir -p "$trial_root/app" "$trial_root/data"
chmod 700 "$trial_root/data"
tar -xzf dialogexa-evaluation-linux-arm64.tar.gz -C "$trial_root/app"
chmod 755 "$trial_root/app/Dialogexa.Api"
cd "$trial_root/app"
DX_DATA_DIR="$trial_root/data" ASPNETCORE_URLS=http://127.0.0.1:18760 ./Dialogexa.Api

Leave that terminal running. In a second terminal, check the endpoint:

curl --fail http://127.0.0.1:18760/api/health

You should receive JSON with status: "ok". This build reports realModelEnabled: false and pushEnabled: false.

Open these addresses in a browser on the server:

Customer trial: http://127.0.0.1:18760/chat/index.html?platform=demo-shop
Admin workspace: http://127.0.0.1:18760/admin/index.html

For a server without a desktop browser, use SSH forwarding from your computer and open those same local URLs:

ssh -L 18760:127.0.0.1:18760 your-user@your-host

Replace the example account and hostname with your own. This assumes you already have SSH access. If port 18760 is in use on your computer, choose another local port and use it in your browser.

Sign in to your own workspace

On first launch, Dialogexa creates a private admin credential at:

<your data directory>/.secrets/admin-token

View that file in a trusted terminal or private file viewer on your own server, then enter its contents in the workspace credential field. Keep it out of URLs, screenshots, public messages, and web source. The download does not contain credentials for Dialogexa's public demo or provide access to its admin workspace.

The customer page creates its own conversation access credential. To try two separate customers, use separate browser profiles or private windows.

Try an end-to-end workflow

Start a customer conversation, send a sample request, and submit a demo form.
Sign in to your own admin workspace and open that conversation.
Save internal guidance and check that it stays out of the customer view.
Send a direct reply, or write a draft in the customer's language, review it, and send it.
Take over the conversation and confirm that an outdated draft or version cannot bypass the server's checks.
Stop and restart your test process, then confirm that messages and forms are still there.

The trial lets you evaluate a real human collaboration workflow. auto names a conversation control mode; it does not mean an AI model is connected. The demo knowledge and forms are test material, not business pricing or service commitments.

Keep it running and connect a domain

The foreground command is for an initial trial. Closing that terminal stops the application. For a persistent service, have your server administrator create a dedicated systemd unit with a fixed working directory, a separate DX_DATA_DIR, and a non-root account.

A public deployment also needs your own domain, HTTPS access, permissions, and backup plan. Keep the HTTP trial port private. The download does not include Dialogexa's Tunnel credentials or account configuration. Setting up a domain and installing a service are environment-specific steps, not a one-click outcome.

Messages and knowledge live in your SQLite data directory. Before an upgrade, stop writes, take a consistent backup, and keep both the data directory and the previous application release.

Build for another platform

Open VS/Dialogexa.sln in Microsoft Visual Studio, or open the separate AS/Dialogexa.Android project in Android Studio. The shared API contract is in contracts/api-v1.md. Read the project READMEs and check the pinned toolchains before building.

The backend pins .NET SDK 10.0.401 in global.json. The web workspace includes dependency lockfiles for React, TypeScript, Vite, and pnpm. The Android README lists its Gradle Wrapper, AGP, and SDK requirements. The source download uses a portable Node default and relative cache directories. Configure the paths to your own installed tools when needed; Android source accepts HTTPS endpoints.

For example, publish a self-contained Linux x64 backend with:

dotnet publish VS/src/Dialogexa.Api/Dialogexa.Api.csproj -c Release -r linux-x64 --self-contained true -o output/linux-x64

Build the web projects, or use the included web dist files, then place them under the server's publish directory:

VS/web/portal/*                    → publish directory/wwwroot/
VS/web/Dialogexa.Admin/dist/*     → publish directory/wwwroot/admin/
VS/web/Dialogexa.Widget/dist/*    → publish directory/wwwroot/chat/

Preserve the admin and chat directories and their assets when replacing the homepage. Test your rebuilt package on its target machine; the existing ARM64 checks do not validate an x64, Windows, or macOS build.

Official references

The existing ARM64 release has passed server, public API, and persistence checks. Browser interactions, other users' machines, Android devices, and notification delivery require their own validation.