Access Portal
Sign in with your work email, or create a new customer workspace.
Sign in
Enter your customer account email and we will send a secure reset link.
Create customer account
Dashboard
Live fleet overview - gateway health, PLC count, and tag visibility across your workspace.
Gateway Fleet
Gateways available to this workspace.
Selected Gateway
Runtime status, config version, PLCs and tags.
Custom Devices Fleet
ESP32/RPi Pico-class devices reporting to this workspace.
Selected Custom Device
Quick status and I/O snapshot.
Gateways
Register and manage cloud-side gateway records that local middleware binds against.
Account / Workspace
Admin setup for customer accounts. In the self-service flow this is created during sign-up.
Register Gateway
Create the cloud-side gateway record the local middleware will activate against.
Custom Devices
Sensors and boards that don't run the middleware - ESP32, Raspberry Pi Pico, or anything that can send JSON - reporting alongside your PLC gateways.
Device Fleet
Custom devices reporting to this workspace.
Selected Device
Reported I/O, location, and device key.
Register Custom Device
Define what this device reports - field names, types and units - then generate its credentials and firmware snippet.
Middleware Activation
Generate the one-time activation package used by the local PLC middleware to bind itself to this gateway.
Activation Package
One-time token bundle for middleware binding. Copy the JSON to your local middleware config.
{}
Downloads
Download the portable Damark Edge Gateway package and follow the customer installation guide for local setup.
Damark Edge Gateway for Windows
Local industrial connectivity for PLC, BACnet/IP, remote telemetry, and governed command workflows.
Quick start
- Download the package.
- Extract it to
C:\Damark\EdgeGateway. - Run
PlcMiddleware.Host.exe. - Open
http://localhost:5000. - Paste a Middleware License Token generated from this workspace.
Plan & Access
What your workspace's plan unlocks, and what your role lets you do inside it.
Your role: -
What each workspace role can do.
My Users
Workspace users are scoped to this customer company. Tenant owners and admins can add engineers, viewers, billing managers, and other admins.
Company Profile
Everything about your workspace - identity, plan, team, gateways, and license activity - in one place.
Remote Integration Clients
Issue scoped API keys so external dashboards and services can read (and optionally write) live tag data from your gateways - without giving them a Portal login. Each client is limited to the gateways you pick, and how much it can see counts against your plan's remote-integration quota.
Your clients
Click a client to see its scope, key, and controls.
Admin Console
Manage customer workspaces, billing status, and plans without leaving the operations portal.
Middleware Admin License
Generate a short-lived local Admin license for emergency Middleware access on ONE PC. You choose how long it lasts and enter the PC code the Middleware shows on its emergency access screen. Re-enter your platform admin credentials.
Fleet
Every workspace at a glance: who is connected, which version they run and what is over its plan.
Customer Companies
Manage monetization status and plans across all workspaces.
Plan Change Requests
Tenant-submitted upgrade/downgrade requests awaiting your approval.
One-time Licenses
Perpetual offline licenses: approve payments and review requests to move a license to another PC.
Branded copies
Companies that generated a branding file for the free Middleware they hand out. A copy that checks its status loses the logo when its company is revoked, paused, below Professional, blocked here, or its file is invalidated. A file without the check can never be retired.
CORS Origin Requests
Tenant-submitted external dashboard origins awaiting your approval for cross-origin API access.
Company Profiles
Browse every customer workspace's profile - identity, plan, team, gateways, and license activity.
Dev Tools
Manual PLC/tag configuration for testing. In production, PLC connections and tags should come from middleware sync, not portal entry.