Skip to content
Lightning VMBeta

Articles

Before you take an AI-written panel into production

How the project was written, what the README says about itself, and the trials we suggest before you use it with real customers.

About 3 min read · Last updated

Lightning VM's README opens with a warning: the project was written together with AI. This article explains what that warning means and what to do about it in practice.

How it was written

The project's owner described what was wanted, in Turkish, and gave feedback with screenshots; Claude Code wrote the code, the tests, the docs and the installation scripts. Every change went through unit, integration and end-to-end (Playwright) tests and was tried on a demo server.

The README also states the price of this method: it is fast, but it contains code that no human has reviewed. There may be bugs, gaps and security holes.

What is tested

The repository has unit tests, integration tests that run against PostgreSQL and Redis, and end-to-end tests written with Playwright. The end-to-end suite runs against its own temporary installation, with an empty database and the VMware simulator; it is never run against a panel that holds real data. The current test counts and the results of the latest runs are in the "Geliştirme ve testler" table of the README; we do not repeat them here, because they go out of date with every change.

The adapter tests do not run against a real hypervisor but against mock servers that imitate the platform.

What the README says about itself

  • The VMware side was tested mostly with the simulator, not with a real vCenter / ESXi.
  • Of the six new adapters only Incus has run on a real server, and only with containers.
  • None of the five payment providers was tried with a real merchant account.
  • Sending an e-Fatura (to a registered buyer) was not tried with any real integrator.
  • The browser console was never tried with the real VMware SDK.
  • Some of the most recently added screens have not been looked at by a person.
  • It has not had an independent security audit.

This list does not count against the project; it is a to-do list that tells you what to try yourself.

What to do before production

  1. Install it on a separate server and use it with your own team only for a while.
  2. Try your platform. On a test cluster, run an order, a first boot, a reinstall, a resize, a snapshot and a deletion end to end. Details: From the simulator to a real platform.
  3. Try payments. Make one payment and one refund in test mode with the provider you will use. The panel's own test provider (Sandbox) must be off once there are real customers.
  4. If you will use Turkish e-invoicing, send an invoice in your integrator's test environment and confirm the fiscal points in the docs with your accountant.
  5. Try backup and restore. Take backup.key off the server and restore a backup onto an empty server. Details: Updates, backups and restore.
  6. Switch two-factor authentication on for admins.
  7. Before every upgrade, read upgrade-notes.md; billing and sign-in behaviour can change between versions.
  8. Have the code read, especially the parts that deal with money and identity.

Backups of customer VMs

The panel's backup is the panel's database; it does not contain your customers' virtual machines. You need a separate backup solution for those.

Contributing

The project is open source (Apache-2.0) and the repository is public. Reporting a bug you find as an issue, or sending the fix, is in the README's words what will make the project trustworthy. For security vulnerabilities, use the route in SECURITY.md instead of a public issue.