Terms of Use
Terms of use for Spooktacular. MIT licensed, Apple EULA compliant, no strings attached.
Last updated: April 12, 2026
Spooktacular is MIT licensed. You can use it for any purpose, commercial or personal, with no restrictions beyond the MIT license terms.
1. The MIT License
Spooktacular is released under the MIT License. The full text:
Copyright (c) 2026 Spooky Labs Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
2. Apple EULA compliance
You are responsible for complying with Apple's software license agreements when running macOS in virtual machines.
Spooktacular uses Apple's Virtualization.framework, which is Apple's official API for creating virtual machines on Apple Silicon Macs. Key points:
- Apple Silicon only: macOS virtualization via Virtualization.framework is only supported on Apple Silicon Macs. Spooktacular does not support running macOS on non-Apple hardware.
- macOS EULA: The macOS Software License Agreement permits running up to two (2) additional copies of macOS in virtual machines on each Apple-branded computer. Spooktacular enforces this limit via CapacityCheck.swift.
- Restore images: Spooktacular downloads macOS restore images (IPSW files) from Apple's official servers. These are subject to Apple's software license agreements.
- Your responsibility: You are responsible for ensuring your use of macOS virtual machines complies with Apple's current EULA. Spooky Labs does not provide legal advice.
3. VM data responsibility
You are solely responsible for all data stored in your virtual machines, including:
- Source code, build artifacts, and CI/CD outputs
- Credentials, tokens, and secrets injected via provisioning scripts
- Any software installed inside VMs
- Backups and disaster recovery of VM data
Spooktacular stores all VM data locally at ~/.spooktacular/. We do not access, back up, or manage this data.
4. Enterprise use
Spooktacular is suitable for enterprise use under the MIT license. There are:
- No per-seat restrictions
- No per-core licensing
- No usage limits
- No commercial use restrictions
- No requirement to purchase support
- No requirement to disclose your usage
For enterprise deployments at scale, we recommend:
- Pinning to a specific version (see Versioning)
- Running your own fork if you need guaranteed availability
- Contributing upstream fixes to benefit from community maintenance
5. No warranty
As stated in the MIT license, the software is provided "as is" without warranty of any kind. Spooky Labs is not liable for any damages arising from the use of the software.
6. Third-party software
Spooktacular depends on Apple's Virtualization.framework and other system frameworks. These are subject to their own licenses and terms. Any software you install inside virtual machines (Xcode, Homebrew, GitHub Actions runner, etc.) is subject to the respective licenses of that software.
7. This website
This website (spooktacular.app) is provided for informational purposes. While we strive for accuracy, feature descriptions reflect the current state of the software and may change between releases. Always refer to the source code for the authoritative implementation.
8. Changes to these terms
We may update these terms from time to time. Changes will be posted on this page with an updated date. The MIT license itself will not change.
9. Contact
Questions about these terms? Open a GitHub Discussion.