The Dyverso domain is the place where the simulation happens, it provides the physics to move the fluid and carries the particles that represent the fluid's body:

The domain is not visible, there is no viewport icon, and it is adapted automatically, so the fluid can expand without boundaries.
The actual point of emission is determined through the position of a Dyverso → emitter.
Dyverso particles can be influenced by almost the entire range of → daemons.
All fluid-related settings (viscosity, density, etc.) are made under the domain's → "Particles" parameter set.

The Dyverso domain icon used in a simulation. Simulation and render done by Victor Sanchez, Next Limit Technologies.

You can choose between two fluid types: "Liquid - PBD" and "Liquid - SPH". Both types support GPU-based simulations:

PBD is the abbreviation for "Position Based Dynamics, a fast method for the creation of different fluid types. Currently, only liquids are supported.
SPH stands for "Smooth Particles Hydrodynamics". This technology is related to RealFlow's → SPH standard particles, but the Dyverso method is much faster.
Since both types have completely different backgrounds the results of your simulations will differ as well. Anyway, the level of detail you can achieve with SPH is often higher, but depends on parameter's like "Resolution", emitter speed and "V/H random". With a sufficient amount of PDB particles it is possible to get almost the same level of details as with SPH fluids.

Working with Multiple Domains

It is possible to add more than one Dyverso domain to a scene, and their particles are also able to interact (this feature requires at least RealFlow version 9.1.1.0186). In order to assign a Dyverso emitter to a specific domain you have to connect them in the → "Relationship Editor". Here is a typical setup with three domains and several emitters:

Emitters must be unlinked from the → hub node (select one or more connections with the mouse and press Del).
To link specific nodes draw a line between them with a pressed Ctrl/Cmd key.
Daemons can also be linked individually to make them act on specific domains only.
"Gravity01" acts on all domains, because it is connected with the domains via "Hub01".
The simulation of multiple domains does not support OpenCL/CUDA at the moment.
Unlike the → standard particles system, Dyverso does not provide a → Container node. Instead of a Container just use a second domain, and make sure that both domains share the same → "Resolution" parameter.

Browser not supported