Enterprise
The Enterprise service is a media production service operated by Displayhome for agencies, networks, portals and marketplaces.
Overview
Listings come in from the systems you already run. A media kit in your signature comes back, ready to publish.
Scale
Production runs asynchronously and in parallel across your whole inventory, and delivers into the storage and publishing systems you already run.
Fidelity
Every output is verified against the source photographs before delivery. An output that deviates from the source is reprocessed, not delivered as is.
Signature
Your brand and editorial rules are defined once with your team, versioned, and applied to every listing without further input.
Enterprise is not the App at scale. The App is operated by your team, one property at a time. Enterprise runs on your whole inventory, under a production signature agreed with you and operated by Displayhome.
Service model
Four things are agreed at integration: where your listings come from, the production signature, the media kit, and where it is delivered. Displayhome then operates production end to end.
Signature setup
The production signature is your media standard. It is approved once, versioned, and applied to every listing.
Brand and editorial rules are not redefined for every listing. Listing-specific production decisions are made within the approved signature.
| Element | Definition | Format |
|---|---|---|
| Logo | Placement, size, appearance rules, light and dark variants | SVG · PDF (vector) |
| Colours | Palette for captions, cards and overlays | hex #RRGGBB · brand guide |
| Typography | Caption and title typefaces, sizes, casing | Font files with a licence covering video use |
| Language and captions | Publication languages; data shown in captions (price, surface, agency) | Caption rules; examples of listing copy |
| Editorial rules | Order and tone of the information in the media | Editorial guidelines |
| Editing | Duration, pacing, transitions, music | Reference films; licensed library or own licensed track |
| Opening card, end card, CTA | Film open and close; call to action and its destination | Listing URL, phone number, website, or none |
| Output formats | Formats in every kit, optional formats, channel-specific requirements | List of channels; aspect ratios and resolutions |
Several brands, several signatures. One signature per brand or agency; the listing’s agency field selects it.
Inputs
Listings are pushed by your systems as structured data. For low volumes, a public listing URL is accepted instead.
| Method | Definition | Format |
|---|---|---|
| API-based integration | Your CRM, transaction software or back office pushes each listing on publication and on update. The payload contract is agreed during integration. | JSON · HTTPS · contract agreed at integration |
| Listing URL | The public listing page is read for the same fields. Missing or ambiguous fields are reported to you before production starts. Suited to low volumes and trials. | string · absolute URL · https |
The data model below is illustrative, not a public contract. The field set is agreed during integration and extended with fields from your system where useful - internal reference, mandate type, energy rating, agent in charge.
| Field | Definition | Format | Required |
|---|---|---|---|
| listing_id | Primary key of the listing in your system. Used for file naming, versioning and delivery tracking | string · unique · max 64 chars | yes |
| images[] | Ordered set of source images. Order is used as a hint for the walkthrough sequence | array<file | url> · 3–40 · JPEG, PNG, WebP, HEIC · ≥1920 px long side | yes |
| title | Listing title, as published. Drives the opening card and captions | string | yes |
| location | City or district, as published. Drives captions and the end card | string | yes |
| surface | Living surface, in square metres | float · m² · > 0 | no |
| price | Asking price, in the listing currency | integer · major units · currency ISO 4217, fixed upon service agreement | no |
| description | Free-text description, as published. Used for room identification and caption wording | string · UTF-8 | no |
| agency | Agency or brand code. Selects the production signature on multi-brand accounts | string · matches a configured signature | no |
| listing_url | Public URL of the listing. Call to action on the end card | string · absolute URL · https | no |
{
"listing_id": "AG-2026-01842",
"title": "Apartment with terrace, Paris 6",
"location": "Paris 6",
"surface": 260,
"price": 4950000,
"agency": "your-agency",
"listing_url": "https://your-agency.com/listings/AG-2026-01842",
"images": ["https://cdn.your-agency.com/01842/01.jpg", "https://cdn.your-agency.com/01842/02.jpg"]
}
Production
Each listing is processed as one set of related photographs: understood as a whole, then selected, produced, verified and delivered.
Quality & fidelity
Production uses generative systems. Fidelity is verified on every output.
Production uses generative models, so every output is verified against the source photographs before delivery. An output that deviates from the source is reprocessed; it is not delivered as is.
Preserved elements
- The architecture of each space
- Visible objects and furniture
- Spatial characteristics - proportions, openings, volumes
- Room identity
- Significant visual landmarks
- Consistency with the source listing media, in every format
Where a vertical adaptation would introduce content absent from the source, a crop is used instead.
Fidelity and home staging are different services. Home staging - furnishing or emptying a room - changes what a room contains, and belongs to the App. Enterprise production, as documented here, preserves the property as photographed.
Outputs
Each listing is delivered as a media kit defined in the signature.
Remastered| Format | Aspect | Duration | Resolution | Container · codec | Captions |
|---|---|---|---|---|---|
| Tour film | 16:9 | 30–60 s · set in the signature | 1920 × 1080 · 3840 × 2160 on plans that include it | MP4 · H.264 · AAC stereo | Burned in; SRT file on request |
| Vertical film | 9:16 | 15–30 s · set in the signature | 720 × 1280 · 1080 × 1920 | MP4 · H.264 · AAC stereo | Burned in, within the platform safe zone |
| Remastered photographs | original · 9:16 | - | original size · 1080 × 1920 (9:16) | JPEG · q90 | - |
Optional formats follow the same container and resolution once included in the kit. Formats and durations outside this table can be set in the signature on request.
{listing_id}_{format}_v{n}.{ext}
AG-2026-01842_16x9_v1.mp4
AG-2026-01842_9x16_v1.mp4
AG-2026-01842_photo-03_v1.jpg
AG-2026-01842_photo-03_9x16_v1.jpg
Integrations
Inputs and delivery destinations are connected once, during integration, with your technical team.
- APIs - your CRM, transaction software or back office pushes each listing on publication: Salesforce, HubSpot, Hektor, Apimo, Netty, or your own platform
- Listing URLs - the public page of the listing on your website or portal, for low volumes and trials
- Your storage - an S3-compatible bucket, an SFTP server, or a shared folder such as Google Drive, SharePoint or Dropbox
- Your publishing systems - the CMS behind your website, such as WordPress, Webflow or a headless CMS; a media library such as Bynder or Cloudinary; the back office of your portal
- A webhook - an HTTPS notification to your endpoint on each delivery, carrying the listing identifier, the version and the file locations
- The Displayhome private dashboard at
private.displayhome.ai- download per listing
No single mandatory API. The connection is defined with your technical team from what your systems can export and receive. A delivery method already in place on your side - an existing feed, a media library, an internal API - can be integrated on request.
Service levels
Production is asynchronous and parallel. Each listing is delivered within the service window agreed in your contract.
| Item | Definition |
|---|---|
| Delivery | A listing received with complete inputs is delivered with its kit within the agreed service window - currently a 24h delivery window. |
| Modification in case of a problem | We will send you a notification if we are not able to process your request. |
| Redelivery | A corrected kit is delivered at the next window, as a new version of the same files. |
| Reporting an issue | From the listing in the dashboard, or by email to your support contact, named at onboarding. Include the listing identifier, the format and the timecode. Acknowledged within one working day. |
Service window, priority and support levels are stated in your service agreement.
Infrastructure
Where production runs, how it runs, and which models it uses.
Anything not stated here - regions, retention, security controls - is covered in the technical documentation shared during evaluation, or defined in your agreement. This page does not make claims it cannot document.