A waitlist is an access request, not an account or an API key. Skyfall’s product page offers an early-access waitlist; the access-request steps below explain how to reach it. This independent guide does not enroll applicants, distribute credentials, sell subscriptions, or host the model. Public demonstrations and research results explain the system; they do not establish the commercial terms of using it.
What is confirmed, and what is not established?
The distinction below reflects the official product page and the October 19 research article reviewed for this guide. “Not established” means those sources do not give us a verified basis for the claim—not that an option cannot exist through a private arrangement or later release.
| Question | Established in this review | Still to confirm |
|---|---|---|
| How do I request access? | An official early-access waitlist. | Eligibility, invitation timing, capacity and access duration. |
| Can I try a demo? | Published CAD and BIM showcases, with interactive research examples. | A self-service session accepting your own inputs. |
| Is there a public API? | A description of the model’s pipeline, not a verified API contract. | Endpoints, authentication, supported inputs, output schemas and limits. |
| What does it cost? | Reported benchmark task costs. | Commercial prices, billing units, quotas and trial conditions. |
| Can I download it or run locally? | No verified distribution or local deployment terms in this review. | Official packages or weights, hardware requirements and deployment rights. |
| Is SKY-001 open source? | The research article describes the approach. | An official code or weights release and the license governing each. |
Use the official route, not a lookalike download.
- Open Skyfall’s official SKY-001 waitlist page (external: skyfall.ai) and use its waitlist control. Follow the instructions currently shown there; this guide does not reproduce a form that may change.
- Review the terms and data notice before submitting information. Do not upload confidential drawings or customer files merely to demonstrate interest.
- If Skyfall responds, confirm whether the offer covers a guided demonstration, a hosted trial, an API, or another arrangement. Record its scope before planning an integration.
A public showcase can help you choose questions, but watching a saved rollout is not the same as generating an artifact yourself. An invitation also should not be assumed to include every capability shown in research.
Benchmark cost is not a price list.
Skyfall’s research article reports costs for defined CAD and BIM construction tasks; see the primary sources. Those figures do not specify a subscription, a price per API request, an enterprise minimum, or the cost of your complete workflow. Our benchmark methodology guide explains the task boundaries and comparison arithmetic.
Ask for cost per accepted deliverable: include rejected attempts, revisions, integration work and engineering review. A low generation cost cannot tell you how much it costs to obtain a usable part or floor plan.
Arrive with one small, measurable brief.
This is a proposed preparation checklist, not a tested onboarding procedure. Select a non-sensitive example you have permission to share. Write down the input, required output and acceptance criteria before seeing a demonstration.
- Mechanical work: specify dimensions, units, mating interfaces and the required editable artifact. Use the CAD evaluation workflow to separate visual geometry from tolerances and feature-history requirements.
- Building work: specify an envelope, room programme, adjacency requirements and the intended handoff. The BIM evaluation workflow distinguishes floor-plan drawings from structured building elements.
- Evidence: request the generated artifacts, relevant intermediate states, failure cases and measured review time—not only a polished screen recording.
Set a pass condition your team can actually inspect. For example, a promised editable deliverable must open and support the required changes in your intended tool. A visually similar render alone would not satisfy that condition.
Questions for engineering, security and procurement.
Integration and ownership
- Which features are available in this offer, versus on the roadmap?
- Which file formats, units and editable structures are supported?
- Who owns outputs, and what commercial-use rights apply?
- For an API offer, how are jobs, errors, versions and rate limits handled?
Data and service terms
- Are submitted designs retained or used for training?
- Where are data processed, who can access them, and how are they deleted?
- Which confidentiality and security commitments are contractual?
- What support, billing and service commitments apply to the evaluation?
These are questions to resolve, not allegations about Skyfall’s practices. Keep sensitive work outside the evaluation until your organization has approved the answers.
Access questions, answered carefully.
Does joining the waitlist guarantee immediate access?
No. The waitlist establishes a request route, not an invitation date, guaranteed eligibility or service entitlement. Only Skyfall can confirm your access.
Does publishing research mean the model is open source?
No. A description of architecture is different from releasing code or model weights under a license. Verify the publisher, artifact and license before treating any download as official.
Can I assume a trial includes editable CAD or BIM export?
No. The research places executable CAD operations, editable feature histories and editable BIM elements under future work. Read how SKY-001’s visual design plan differs from an executable model, then confirm the deliverables in the specific offer.
Primary sources and review boundary.
Skyfall’s product page supplies the official access route. Introducing SKY-001 supplies the architecture, demonstrations, benchmark claims and roadmap. This is a public-source review, not a trial report or an exhaustive inventory of private commercial arrangements.