Deployment
Containerized application services managed under infrastructure-as-code across physically separated staging and production environments.
Explore the architecture, governance, and information boundaries that support XylaWorks. This page is for procurement, IT, security, privacy, and compliance teams evaluating the platform.
XylaWorks runs on Microsoft Azure. Its architecture uses managed identity for service authentication, private networking for data and AI services, and encryption in transit and at rest. Staging and production environments are separated, with controlled promotion between them.
Containerized application services managed under infrastructure-as-code across physically separated staging and production environments.
Managed relational databases, caches, and document stores isolated on private endpoints, with centralized vault secrets kept out of application code.
End-to-end application telemetry and insert-only, immutable audit logging across the application, worker, and AI execution layers.
Cloud managed identity authenticates inter-service communication. Application secrets and database credentials reside in centralized vaults and are injected at runtime without hardcoding.
Data stores and enterprise AI services are reached over private networking endpoints rather than exposed to the public internet.
TLS 1.3 protects traffic in transit across public and internal endpoints, and AES-256 encryption protects databases, caches, and storage volumes at rest.
Web applications use HTTPOnly session cookies so authentication tokens are not exposed to client-side scripts.
Generated career intelligence outputs pass through structural validation and dedicated content safety filtering before release.
Audit records are insert-only at the application layer. AI executions, seat activations, advisor record views, and approval transitions are logged with actor and timestamp.
Staging and production operate as separated environments, with verified release candidates promoted through gated deployment workflows.
The assessment engine applies the XylaWorks 3-Dimensional Leader Framework — Demonstrated Competence, Professional Credibility, and Meaningful Contribution — through governed processes, scoring logic, and enterprise AI services. Its architecture supports continued improvement while maintaining consistent inputs, governed scoring, traceable outputs, and controlled processing. Zero candidate data is retained by model providers or used to train foundation models.
AI-generated deliverables follow a three-state approval architecture enforced at the database layer — processing, awaiting approval, and approved — alongside structural schema checks and content safety filtering. Governance operates at the system level; it does not mean that a person manually reviews every candidate output.
Organizations work with XylaWorks in different ways. An organization's approved account and each user's server-enforced permissions determine what information they can access. Selecting an organization category during signup or inquiry routes the request only and never grants data access on its own.
| Information | Employer | Organizations & associations | Institution | Workforce program |
|---|---|---|---|---|
| Access and engagement reporting | Aggregate-only counts (cohorts of 5+); never individual redemption identity | Aggregate relationship reporting; no individual candidate accounts | Aggregate and candidate-level information, as authorized | Aggregate and candidate-level information, as authorized |
| Individual candidate outputs (Score, Career Strategy, My Resume, What to Say) | Not visible | Not visible | Permitted outputs visible read-only to authorized staff | Permitted outputs visible read-only to authorized staff |
| Individual scores and score history | Not visible | Not visible | Visible read-only to authorized staff | Visible read-only to authorized staff |
| Submitted material metadata vs. raw uploaded files | Not visible | Not visible | Metadata only (titles, dates); raw uploaded files and edited drafts not visible | Metadata only (titles, dates); raw uploaded files and edited drafts not visible |
| Candidate's private reflections and assessment responses | Not visible | Not visible | Not visible | Not visible |
Authorized institution and workforce staff can view the candidate outputs made available for advising and coaching — Score, Career Strategy, My Resume, and What to Say — along with metadata on submitted materials. Every advisor view of an individual candidate record is recorded and visible to the candidate in their account access log.
Every candidate owns their XylaStudio account and retains their generated career work across school, program, or employment transitions — especially when registered with a personal email address. Leaving an organizational cohort ends future visibility without deleting the candidate's account; permanent account closure is controlled separately by the candidate on the account deletion page.
Chapters, campus clubs, and regional affiliates operate as independent accounts; listing a national organization or affiliation is descriptive only and never shares seats or candidate records. Changes in a candidate's score show observed movement between assessments and do not, by themselves, establish what caused that movement.
Institutions and workforce programs purchase seats for candidates. Employers sponsor seats — activated by candidates with access codes — to support employees through career transitions. Associations, student organizations, and other community groups may introduce XylaWorks to their communities without purchasing seats. Each arrangement and its applicable agreement define how access is provided.
A seat entitles one candidate to the sponsored XylaWorks experience; an access code is the mechanism that activates that seat rather than a standalone commercial unit. XylaWorks does not recruit, staff, place, schedule, dispatch, or manage workers for organizational customers.
XylaWorks structures its security and governance controls around the AICPA Trust Services Criteria, with mappings to NIST CSF 2.0 and ISO/IEC 27001:2022 Annex A across twelve core policy domains:
XylaWorks has completed gap assessments against the AICPA Trust Services Criteria (SOC 2) and ISO/IEC 27001. Independent SOC 2 Type II attestation and ISO/IEC 27001 certification are on the roadmap; neither is claimed as completed today.
Subject-rights tools and data-handling practices support applicable privacy requirements, including self-service candidate data export and documented account deletion workflows with a 30-day grace period.
Audience-scoped reporting boundaries are enforced at the data layer. Institutional privacy requirements — including student record handling under applicable frameworks — are reviewed during procurement for each deployment.
A completed HECVAT (Higher Education Community Vendor Assessment Tool, v4.1.6) covering Organization, Product, Infrastructure, IT Accessibility, AI, and Privacy is available to institutions and workforce programs on request via the technical briefing form.
Connect with our team for a technical briefing covering architecture, reporting boundaries, and compliance documentation for your organization.
Confidential. Scoped to your organization's review.