System families
Solid aluminium, perforated façades, laser-cut screens, fins and battens, honeycomb panels, mesh and expanded metal, weathering steel, and UHPC/GFRC pathways.
International Specification Records / Global
This record organises the façade division around system families, project interfaces, evidence, drawing control, samples and tender requirements.

Direct answer
Select the façade family by architectural role first—cladding, screening, shading or sculptural surface—then resolve substrate, support, panel geometry, finish, exposure and evidence around the actual project.
Project decision
Use these points to structure the first project conversation. Final suitability stays tied to the actual site, selected system and local project team.
Solid aluminium, perforated façades, laser-cut screens, fins and battens, honeycomb panels, mesh and expanded metal, weathering steel, and UHPC/GFRC pathways.
Substrate, secondary steel, brackets, movement, panel joints, openings, corners, soffits, drainage and adjacent trades require project coordination.
Material data, finish information, drawings, samples, mock-ups and performance evidence should be assembled around the exact selected family rather than generic division claims.
Comparison matrix
Use the division comparison to shortlist, then build the system-specific technical pack.
| Field | Apollo façade pathway |
|---|---|
| Role | Cladding, screening, shading, architectural surface |
| Materials | Aluminium, mesh/expanded metal, weathering steel, UHPC/GFRC and selected composite constructions |
| Geometry | Flat, folded, perforated, laser-cut, finned, formed or mesh |
| Finish | System-specific coating / material finish |
| Evidence | Project and exact-system specific |
| Local responsibility | Substrate, secondary support, engineering and installation unless scoped otherwise |
Project brief
Frequently asked
No. Build-up changes by material family, geometry, support and project requirements.
Yes. Concept geometry can be reviewed against fabrication and system constraints.
No. Evidence must be tied to the exact product/system and project context.
Next step
Send the site, dimensions, intended use, quantities and known local requirements. Apollo will review the relevant product pathway and keep local engineering, approvals and site-work responsibilities explicit.