A company with context.
A name, a web presence, and consistent identities that make the exercise feel connected from the first invitation to the final task.
THE SCENARIOIN DEVELOPMENT · BUILT FOR LAB PEOPLE
Bring domains, websites, email, and lab identities together for connected, end-to-end labs and customer demonstrations.
For lab proctors, sales engineers, and technical trainers.
nyclab.net
Illustrative concept · not a live product dashboard
01 / THE IDEA
Give every part of your demo a connected, real-world context.
We’re building Lab Alias to bring the pieces together: a demo organization, a working domain, a website, and lab email addresses that connect to the people taking part.
Prepare the organization once. Give your workshop a shared story. Spend your time on the experience you came to teach.
A name, a web presence, and consistent identities that make the exercise feel connected from the first invitation to the final task.
THE SCENARIOOrganizer-managed aliases map participants’ lab addresses to their existing inboxes, keeping workshop identities separate from work account identifiers.
THE PEOPLEWorking web and DNS resources give your lab something tangible to configure, verify, monitor, and troubleshoot.
THE ENVIRONMENT02 / THE PLANNED WORKFLOW
Built around the organizer.
Designed for the whole class.
Bring a lab domain and build your demo organization around it, with a website and the DNS records your exercise needs.
Prepare lab identities for your roster and map their email aliases to the real inboxes where invitations should arrive.
Use those identities and resources in your chosen platforms, then plan what to keep, reset, or retire after the event.
03 / WHERE IT FITS
Give a customer group a dedicated lab identity and a common company scenario.
Prepare a class roster and teach against resources you control.
Carry a consistent business story across the products you demonstrate.
A FEW PRACTICAL DETAILS
Lab Alias is in development. This page introduces the project and its planned workflow. If you organize labs or demos, email us about your setup — we’d like to learn what would make it useful for you.
The intended workflow is managed by a proctor or organizer for a participant roster. Participants receive messages in their existing inboxes; they don’t need to build their own alias collection.
No. A lab alias is a separate email identifier. Authentication, domain acceptance, licenses, and account provisioning remain subject to the platform you use. SSO requires a configured identity provider.
Retirement is part of the planned workflow. Turning off forwarding doesn’t revoke a vendor account, so account access, domain claims, and recovery addresses need to be considered before an organization is retired.
LET’S BUILD A BETTER LAB DAY.
Tell us what you teach, which platforms you use,
and where account setup gets in the way.