FAQ
Organisations
For studios, galleries, schools, agencies, and institutions that need consistent outputs, clear licensing artefacts, and a provenance trail that holds up when files move between people, tools, and channels.
Do you support teams and roles?
The roadmap includes organisation-friendly access patterns (role-based workflows, least-privilege access, and clear ownership). For now, PixlKey focuses on creating consistent artefacts and identifiers that remain useful regardless of who runs the export.
What outputs are useful for audits or client delivery?
- Watermarked derivatives suitable for distribution and review.
- Licence/certificate-style artefacts for records and hand-off.
- Identifiers/fingerprints that help validate “this file matches that work”.
- Verification-ready assets for later provenance checks.
Can we handle licensing at scale?
PixlKey’s approach is to attach licence details to a specific work and produce repeatable, consistent artefacts. That’s the foundation for handling volume: standard inputs, standard outputs, and fewer “what did we ship?” mysteries.
How does PixlKey fit into an existing workflow?
- Use PixlKey as the “final-mile” processing step before distribution.
- Keep originals private; share only derivatives intended for circulation.
- Include the generated artefacts alongside client deliverables.
- Use identifiers for verification when questions come up later.
Does a watermark guarantee protection?
No tool can prevent copying. PixlKey is designed to make attribution and provenance easier to demonstrate, and to reduce ambiguity when files are reposted, resized, or passed between teams.
What about privacy and sensitive work?
A common best practice is to keep originals internal, and publish only the derivatives you intend to circulate. PixlKey is built around that mindset: controlled exports, clear artefacts, and a defensible paper trail.
Need organisation-specific guidance?
If you’re operating as a studio, gallery, school, or agency, tell us what your workflow looks like (volume, hand-off patterns, licensing needs, and who needs to verify later). We’ll point you at the best-fit PixlKey approach and documentation.
Tip: The cleanest organisational pattern is: keep originals private, distribute derivatives, and file the licence/certificate artefacts alongside the job record. When questions arrive months later, you’ve got receipts — not rumours.