Portfolio DAM and Axle AI: watching the servers your creative teams rely on

Published 2026-11-12

Portfolio DAM, the asset manager many design, marketing and publishing teams still know as Extensis Portfolio, has a new home and a new release. Axle AI, which makes AI-powered media asset management for video teams, took over Portfolio this year, and Portfolio 4.2 came out on 10 November with faster search and updated components. The next FrontierStack release supports the whole Axle line, so the servers your creative teams depend on sit on the same dashboard, and raise the same alerts, as the rest of your infrastructure.

What's supported

A new Media Asset Management section in FrontierStack's service catalogue lists Axle AI's products (Portfolio DAM, Axle AI MAM, Axle AI Tags, Axle Connectr, Axle AI Cloud and Axledit) next to ResourceSpace. The three you run on your own hardware get a live monitor that watches as many servers as you have:

• Portfolio DAM: FrontierStack checks that the Portfolio REST API answers (port 8090, or 9443 with HTTPS) and that Portfolio Administration is up (8091, or 9453). Give it a Portfolio user and it also reads the server's error list, the catalogues that user can see and how many jobs are running or queued. It signs out in the same check, so it holds a licence seat for a moment, not all day.
• Axle AI MAM: FrontierStack checks that the Axle AI web app answers at /axleweb, on a Mac or on Axle's Linux appliance.
• Axle AI Tags: FrontierStack checks the Tags API and, with a Tags user, which AI modules are running: faces, logos, objects, scenes and text recognition.

Problems become alerts through the channels you already use, and FrontierStack's AI Administrator can answer questions such as "are the DAM servers healthy?" from the same readings.

Use cases

A brand or marketing team running Portfolio

Portfolio is licensed per seat, and when every seat is taken the next person simply can't sign in. A lapsed subscription is quieter still: the server keeps running in read-only mode for a grace period, and nobody notices until an upload fails. FrontierStack signs in on a schedule, so a refusal for no free licence seat reaches IT as an alert, not as a message from a designer on deadline. Errors Portfolio reports about itself, such as a vault it can't reach, are raised the same way.

A post-production house running Axle AI MAM on a Mac

On a Mac, Axle AI MAM is a web app on the Mac's own Apache, with PostgreSQL, Elasticsearch and Java alongside. Apache, PHP and PostgreSQL are what FrontierStack manages every day. One detail matters straight away: current macOS no longer includes PHP, which the Axle installer expects Apache to have. FrontierStack notices an Axle install with no PHP and points you to the PHP pane, where you give Apache a PHP module. From then on it watches /axleweb, the disks that hold your catalogues and proxies, the NAS or Xsan volumes behind them, and the UPS the server is plugged into.

A broadcaster or archive tagging footage with Axle AI Tags

AI tagging fails quietly. If the face-recognition module stops, footage still comes in; it just arrives without the metadata people will search for later. FrontierStack signs in to each Tags server and alerts when no AI modules are running, and it can watch the Docker containers on the GPU server as a linked server.

A reseller or MSP looking after several clients' media systems

Media teams rarely have full-time IT. If you support several studios, every Portfolio, Axle AI MAM and Tags server across your clients appears on one page with a status line each. Problems arrive as alerts that name the server, and you can ask the AI Administrator what changed before you call the client.

Upgrading to Portfolio 4.2

Portfolio 4.2 updates its PostgreSQL and Java components. After an upgrade, FrontierStack confirms that the API and Administration are back, shows the server's error list, and lists your catalogues and jobs so you can see they are where you left them.

The rest of the stack

An asset server is only as reliable as what's around it. Because FrontierStack also runs that surrounding infrastructure, the same app covers:

• Storage: Synology, QNAP and TrueNAS health, disk and RAID checks, Xsan, and S3-compatible object storage for archive tiers.
• Certificates and access: TLS for Portfolio Web and NetPublish sites, a reverse proxy in front of the server's ports, and Tailscale for editors working remotely.
• Power and network: UPS status and router health, so you know whether a dark server is the server or the building.
• Credentials: KeyRotate keeps service logins out of scripts and can rotate them.

Read-only, and careful with passwords

The monitor never changes a catalogue, asset or job. Passwords are stored in the macOS Keychain. Portfolio passwords are encrypted with the server's own public key before they are sent, as Portfolio requires, and plain HTTP is used only for addresses on your own network.

Getting started

Once the release is out, open Media Asset Management in the sidebar, choose Portfolio DAM, Axle AI MAM or Axle AI Tags, and add a server by its address. A user name and password are optional. We built this from Axle's published documentation; if you run Portfolio or Axle in production, we would like to hear what you want FrontierStack to watch next.

Portfolio DAM, Axle AI MAM, Axle AI Tags, Axle Connectr, Axle AI Cloud and Axledit are products of Axle AI, Inc. FrontierStack is not affiliated with Axle AI.