Client Support and Limitations
This article summarizes current support for custom transform servers in Maltego Graph Browser and Maltego Graph Desktop. Choose the client before you depend on a feature available in only one of them.
Availability at a Glance
| Capability | Graph Browser | Graph Desktop |
|---|---|---|
| Entity properties, display information, notes, links, and custom icons | Supported | Supported |
| Nested / composed entities | Supported | Not supported |
| Entity overlays and weight | Partial | Supported |
| One-entity transform input | Supported | Supported |
| Multiple-entity transform input | Limited | Supported |
| Whole-graph transform input | Not supported | Supported |
| Input constraints | Supported | Supported |
| Basic transform settings | Supported | Supported |
| Global or auth settings | Not supported | Supported |
| Interactive prompts | Not supported | Supported |
| Runtime status messages | Supported | Supported |
| OAuth-authenticated transforms | Not supported | Supported |
| Transform sets | Supported | Supported |
| Custom server as a Hub item | Supported | Supported |
| Machines / macros | Not supported | Supported |
Feature-specific Notes
- Composed entities: Treat transforms that rely on composed entities as Browser-only.
- Overlays and weight: Graph Browser renders icon URL overlays in the southwest position only. Color and text overlays, other overlay positions, and entity weight require Graph Desktop.
- Multiple-entity input: Graph Browser runs the transform once per selected entity rather than sending the selection as one batch.
- Whole-graph input: Transforms that accept
MaltegoGraphare Desktop-only. - Transform settings: Basic settings work in both clients. Global settings and settings marked
auth=Trueare Desktop-only. - Custom server as a Hub item: Both clients support custom servers as Hub items; Graph Desktop requires version 4.12.0 or later.
Planning a Cross-client Transform
For a transform that must work in both clients, use single-entity input and avoid composed entities, non-icon URL overlays, entity weight, whole-graph input, global or authenticated settings, interactive prompts, OAuth, and machines. Test the transform in each target client before releasing it.
Feature availability evolves with client releases. This article describes the current custom-transform-server behavior; consult the relevant release notes when adopting a newly released client feature.