Software & Media Factory

M‑FactoryOne factory for software. One for media.

M-Factory is two separate offerings. The software factory takes a project from requirements to running software, with your team reviewing every stage. The media factory produces images, video, audio and text from one workflow engine. Both run on your own infrastructure.

Two offerings

One name, two separate factories.

They share a way of working: the machine does the groundwork, people decide. They are delivered separately, so you can start with either one or take both.

Software factory

Source code on a dark editor screen

AI-assisted software development across the whole lifecycle, from the first requirement to maintenance, with a person signing off each stage.

  • Requirements, design, build, test, deploy and maintain in one pipeline
  • A human review at every stage
  • Code, tests and documents stay in your own repositories
See the software factory

Media factory

A photo studio with lights and a white backdrop

Generative media from one node-based workflow engine: images, video, audio and text, made from your briefs and brand material.

  • One workflow engine for four kinds of output
  • Saved workflows for jobs that repeat
  • Nothing is used until a person approves it
See the media factory

The two factories are separate products. Each one is delivered and set up on its own.

Offering 01 of 02 · Software factory

Software factory

From requirement to running software, with a person signing off each stage.

The software factory runs the full software development lifecycle. AI does the groundwork at each stage, and the work only moves on once someone on your team has reviewed it.

The lifecycle. Select a stage to see what happens there.

Changes found during maintenance start the next cycle, back at Requirements.

Stage 01 / 06

Requirements

What the factory does
Turns your requests, meeting notes and existing documents into written requirements and acceptance criteria, and lists the open questions.
What your team checks
Your product owner confirms the requirements are complete and correct.
What it hands over
An agreed requirements document with acceptance criteria.

Offering 01 of 02 · Software factory

What stays with you

Everything the factory produces is yours to keep.

The work is done in your environment and handed over in forms your own developers can read, change and maintain.

  1. Source code in your repository

    Code is written into your own repository and reviewed by your developers before it is merged.

  2. Requirements and design records

    Every stage leaves a written record, so the reasons behind the software do not leave with the people who built it.

  3. Automated tests

    Tests written against the acceptance criteria stay with the code and run again on every change.

  4. A record of every approval

    Who reviewed what, and when, is recorded at each stage.

  5. Your standards, applied

    Coding standards, naming rules and review checklists are agreed with your team and used at every stage.

01 Source code in your repository

Code is written into your own repository and reviewed by your developers before it is merged.

02 Requirements and design records

Every stage leaves a written record, so the reasons behind the software do not leave with the people who built it.

03 Automated tests

Tests written against the acceptance criteria stay with the code and run again on every change.

04 A record of every approval

Who reviewed what, and when, is recorded at each stage.

05 Your standards, applied

Coding standards, naming rules and review checklists are agreed with your team and used at every stage.

Offering 02 of 02 · Media factory

Media factory

One workflow engine for images, video, audio and text.

The media factory runs on an open, node-based generative workflow engine installed on your own infrastructure. Each job is a workflow: a chain of steps you can save, adjust and run again whenever the same kind of content is needed.

How a job flows. Select an output to see what it covers.

What goes in

  • A brief or prompt
  • Reference images
  • Brand material
  • A script or source text

Workflow engine

Open and node-based. Each step is a node; a saved chain of nodes is a reusable workflow.

  1. Prepare
  2. Generate
  3. Refine
  4. Review

What comes out

Image

Still images to a brief: campaign visuals, product images on new backgrounds, and banners in the sizes each channel needs.

Typical uses

  • Campaign visuals
  • Product images
  • Banners in several sizes

Nothing leaves the factory on its own. Every output waits for a person on your team to approve it before it is used.

Illustration. The inputs, steps and uses shown are typical examples; each workflow is set up with your team.

Offering 02 of 02 · Media factory

Use cases

Built for content that repeats.

The media factory is most useful where the same kind of content is needed again and again, in many sizes, versions or languages.

  1. Marketing assets

    Campaign visuals and banners in every size each channel needs, from one brief.

  2. Product visuals

    Product images placed on new backgrounds and in new settings, without a new photo shoot each time.

  3. Voice-over

    Narration for videos, training material and announcements, produced from a script.

  4. Localisation

    One campaign adapted into other languages: copy, voice-over and on-screen captions.

  5. Explainers and training

    Short videos that walk customers or staff through a product or a process.

01 Marketing assets

Campaign visuals and banners in every size each channel needs, from one brief.

02 Product visuals

Product images placed on new backgrounds and in new settings, without a new photo shoot each time.

03 Voice-over

Narration for videos, training material and announcements, produced from a script.

04 Localisation

One campaign adapted into other languages: copy, voice-over and on-screen captions.

05 Explainers and training

Short videos that walk customers or staff through a product or a process.

Examples of use. What a workflow produces depends on how it is set up and the material you provide.

Runs on your infrastructure

Installed on your servers. Run by your team.

Matajari delivers M-Factory as software and sets it up in your environment. This applies to both factories.

  1. Your servers or private cloud

    Both factories are installed on infrastructure you control, not run as a shared online service.

  2. Your data stays inside

    Source code, documents, briefs and generated media are stored in your own environment.

  3. Access by role

    You decide who can start work, who reviews it and who gives the final approval.

  4. Every step on record

    Each run, review and approval is logged, so you can trace how any piece of work was made.

  5. An open workflow engine

    The media factory is built on an open engine, so your saved workflows are not tied to a single supplier.

01 Your servers or private cloud

Both factories are installed on infrastructure you control, not run as a shared online service.

02 Your data stays inside

Source code, documents, briefs and generated media are stored in your own environment.

03 Access by role

You decide who can start work, who reviews it and who gives the final approval.

04 Every step on record

Each run, review and approval is logged, so you can trace how any piece of work was made.

05 An open workflow engine

The media factory is built on an open engine, so your saved workflows are not tied to a single supplier.

Getting started

Start with one project or one workflow.

  1. Tell us what you need

    A software project, a content workflow, or both. We look at how your team works today.

  2. Choose a first piece of work

    One application or feature for the software factory, or one repeating content job for the media factory.

  3. We install and set it up

    We set M-Factory up on your infrastructure and agree the review steps and who approves what.

  4. Your team runs it

    Your people use the factory day to day, and we help you extend it to more projects.

01 Tell us what you need

A software project, a content workflow, or both. We look at how your team works today.

02 Choose a first piece of work

One application or feature for the software factory, or one repeating content job for the media factory.

03 We install and set it up

We set M-Factory up on your infrastructure and agree the review steps and who approves what.

04 Your team runs it

Your people use the factory day to day, and we help you extend it to more projects.

Frequently Asked Questions

Everything you need to know about M-Factory.

Two separate offerings under one name: a software factory for AI-assisted software development across the full lifecycle, and a media factory that produces images, video, audio and text.
No. They are separate products. You can start with either one and add the other later.
No. It does the groundwork at each stage. Your product owners, developers and testers review and approve the work before it moves on.
In your environment. Source code goes into your own repositories, and documents and generated media are stored on your own infrastructure.
The models are chosen with you during setup, to suit your infrastructure and your rules on data.
No. In both factories, a person on your team approves the work before it is merged, released or used.
Tell us whether you want to begin with software, media or both. We pick a first project or workflow together, set it up on your infrastructure and agree who approves what.

See M-Factory on your own work

Book a demo and tell us whether you want to start with software, media or both.

Book a Demo