SixPanel release notes

New

• AI Coding. Write what you want changed, and a coding agent changes that one project's code on your server, from a chat in the panel — Claude Code, or Codex when you use a ChatGPT plan. You see every file it reads and every change it makes, with Stop while it works; write again and it continues the same conversation. AI Coding is part of SixPanel Pro.
• AI Coding works on a staging site first. The work is done on a private copy of the project, and the live website is not touched until you press Move to production. Working on a live website directly is offered only where the code does not come from git, and only after you agree to it for that session.
• You choose how much AI Coding may do without asking. Ask before every change, edit files and ask before commands, plan only, or work without asking. Rules for this project holds the commands to always allow, the commands to never allow and your standing instructions.
• Use your Claude or ChatGPT plan for coding. AI → Providers → Add a provider → Subscription: sign in once, on the provider's own page, and AI Coding and Create with AI use your plan instead of an API key. Anthropic and OpenAI allow a plan only inside their own coding programs, so Tia and monitoring keep using an API key or your own endpoint — the page says so before you choose.
• Adding an AI provider is three steps. Choose how — a subscription, an API key, your own endpoint or a model on this server — choose which, and press Connect. Each check is on its own line, with the provider's own error under the one that fails. The first provider that works becomes the Default, and Make default moves it.
• The coding program is installed and kept up to date for you. One button installs it. Every new version is tried on your server before it is used, and the version before it is kept.
• Tia reads your project to answer. "Where is the delivery fee calculated?" — she can search a project's code and read how its database is laid out. To look at the data itself she asks you every time, and shows the exact read-only query first.
• Tia hands code changes to AI Coding. When what you ask for needs the app's code to change, she writes the task down with what she found and starts an AI Coding session on a staging site, with a link to it.
• Tia: Fast, Balanced, Deep. Three buttons under the message box choose how much she thinks before she answers. She also knows every page of the panel — "Where is the firewall?" gets a link — and what each release changed.
• Create with AI can write with the coding program. Where it is installed, a change on a Create with AI website is written by it. The chat, the preview, Publish, History and Undo are as they were.
• A bell for what waits for you. At the top of every page: the changes that wait for your approval, and Needs your attention — one line per thing that is wrong, with the button that opens the page that fixes it. Home keeps one line.
• Confirm it is you — once, not every time. Before an action that gives full control of the server, the panel asks for your 6-digit code alone when two-factor login is on, with no password, and remembers the answer for 5 minutes. Security → Sign-in sets that to every time, 2, 5 or 15 minutes.
• Files: a long action shows how far it is. Compress, extract, copy, move and delete start at once and show their progress, which is still there after a reload. Select rows with Shift and Ctrl, open with a double-click, and use the keyboard: Enter, Delete, F2, Ctrl+A.
• Staging & Testing, inside every project. Test copies are now called staging sites. Every project and website has a Staging & Testing page in its own menu: a private copy of the project to test a change before it goes live. On Projects and Home a staging site is a row inside its project's card.
• Staging on your own domain. When you make a staging site, choose a temporary address or a domain of yours — no AllsWeb account needed. HTTPS is set up for you, and search engines are told to stay away. A staging site on a temporary address can move to your own domain later.
• Staging on its own git branch. For a project deployed from git, the staging site gets a branch of its own. A push to it deploys the staging site, Commit and push sends changes made on the server, and Bring production's commits in keeps the branch up to date.
• Promote to production. When the change is tested, Promote backs up production's database, merges the branch, deploys production with its database migrations and checks that it answers. If anything fails, production is put back as it was. The dialog first shows what will run on production. Open a pull request is there when you prefer a review on GitHub.
• Database changes travel with the code. Migrations run on the staging site first and on production at promote. A Node.js website now has deploy commands too, for example npx prisma migrate deploy.
• An AI agent page in every project. Every project and website has an AI agent page: give Claude Code, Codex, Cursor or another agent that one project, and nothing else on the server.
• Connect your own AI agent in three steps. Pick your agent, press one button, paste the lines it shows. The last step turns green when your agent's first call arrives. AI → Connect does the same for the whole server. Codex is on the list.
• Many projects, many servers. Every connection has its own name, so one agent can hold several projects and several SixPanel servers side by side. The Connections list shows every agent that has a way in, and Remove stops one at once.
• Let an agent work on the server itself. One switch prepares the project's own account for an agent that works in a shell, with a guide the agent reads by itself and the sixpanel command for that project only: status, logs, deploy and restart, and on a staging site changes, commit and promote.
• Tia works with staging sites. She can list, make and refresh them and, when you say yes, commit changes, bring production's commits in and promote.

Better

• A staging site starts only when it is ready. It answers once the panel has checked that it uses its own database. On a 6amMart staging site, payments, SMS, push notifications and email are switched off, and you can sign in on its new address.
• Staging sites for 6amMart, WordPress, Laravel and static websites. For a custom PHP or Node.js app, AI Coding sets a staging site up and you start it.
• Database → Import runs as a job. The page answers as soon as your file has arrived and shows the import step by step. The database as it was is kept first, and a long import no longer ends in an error message while the server finishes it.
• Deleting a project frees its share of the server at once. The projects that remain get its memory and PHP workers with no restart.
• Backups: paste a storage's address as your provider shows it. https:// and anything after the host are sorted out for you, and a bucket in the address fills the Bucket field.
• Every open page reloads by itself after a panel update. Never under your hands: a tab with something typed and not saved shows a Reload bar instead.
• Projects: cards of one height. Every card carries the same three facts — its address, its status and its last deploy.
• In your language. Hundreds of new sentences are translated in all seven other languages, and nearly a hundred that were still English or out of date are corrected.
• On a phone. No page is wider than its screen in any language, and every button is easy to press. The log's Expand and Close buttons stay on the screen, and the language menu opens inside it.
• In Arabic and with a screen reader. English that comes from the server reads correctly on an Arabic page, the built-in backup storage is named in your language, and more fields — the PHP and Node.js version pickers among them — have names for screen readers.

Fixed

• Installing on a new Ubuntu 26.04 server. The one-line install no longer stops halfway when it is run by a user who is not root. Installing as root and updating from the panel were not affected.
• Smaller fixes. A new WordPress website no longer shows a failed task before it has an address, a deleted task leaves nothing on the check-up, saving a website's settings unchanged changes nothing, the Files page of a website with no code yet says what to do, a file action that takes minutes is no longer shown as failed, and deleting a website also removes the temporary files its account left on the server.
• Security hardening. Several protections were tightened. Updating is recommended.

New

• A clearer, faster install. The installer shows numbered steps with live progress and ends with your panel address and sign-in details. Measured on a new 2-CPU server: about 75 seconds from start to finish.
• Move a 6amMart shop to another server. Migration now sends the whole shop, and it arrives running and already on HTTPS. Measured: about seven minutes per shop. Websites stay on the old server and keep running, and Migration names them before you start.
• Test copies of any project. Create test copy makes a separate copy of a shop or website on a temporary address, to try an update safely. A shop's copy has payments, SMS and push notifications off by default.
• Server → Database. One place for the database server: status, every database, your own settings, time zone, and Open in phpMyAdmin already signed in.
• Build with AI, live. Edits show up in the preview in about 0.1 seconds, Publish puts the site live when you are ready, every change can be undone, and you can connect git.
• A terminal in the panel. Server → Terminal opens a shell in the browser, and every project and website gets its own. Optional key-only SSH access per project, and SSH can be turned off for the whole server.
• Addons, starting with 6amMart. The new Addons page installs the 6amMart addon, which then updates with SixPanel. Servers and shops that ran SixPanel before addons keep working as they did.
• SixPanel Pro. AI features are part of SixPanel Pro, and everything else stays free. Includes AllsWeb AI with no key to paste, a 14-day free trial and Pro coupons.
• Connect your AllsWeb account. Settings → AllsWeb account links the panel to allsweb.com. Back up to AllsWeb Storage with no keys to copy.
• Report a problem from any page. The flag at the top of every page sends a report to AllsWeb support, with a preview of what is sent. sixpanel report "what happened" works even when the panel is down.
• Cloudflare, by account. Settings → Cloudflare shows each account and site, applies recommended settings in one click, and sets up new domains by themselves.
• More PHP and Node.js versions. Server → PHP and Server → Node.js add versions when a website needs one, and a website can move between them.
• An Environment page for PHP websites. Edit the .env values of a Laravel or other PHP website in the panel. Quotes are added for you, only the lines you change are rewritten, and a line the app cannot read is named and fixed in one press.
• Largest tables and slow queries for every website. A website's Database page lists its ten largest tables, and Slow queries shows the statements that take more than a second.
• SixPreflight is now SixChecker. Same project check-up, new name.

Faster

• A faster customer website. The 6amMart storefront now serves first-time visitors and sudden crowds from a short page cache. Measured at 100 visitors a second, the slowest requests dropped from 6 to 9 seconds to about a hundredth of a second, and it uses about 80 MB less memory.
• Faster panel. Pages open sooner, the panel stays responsive during heavy work, and it starts faster on servers with many websites.

Fixed

• Smaller fixes. Leaving the first-run setup now sticks, a deleted project's addresses are free at once, alert emails are sent again when refused, the panel keeps working when the disk is full, Health and the update dialog are clearer, a shop moved to a server on another time zone keeps its times, a project takes no changes while it is being moved, a website's address page is named Domain & SSL like a shop's, and many fixes to moves, backups, certificates, file manager, Tia and the sixpanel commands.
• Security hardening. Several protections were tightened. Updating is recommended.

• Connect Claude in one step. AI → Connect → Connect Claude creates a ready token and shows the settings to paste.
• Edit an MCP token. AI → Connect → Tokens → Edit changes a token's name, permissions, projects and expiry without replacing it.
• Clearer answers for AI agents. When an agent is not allowed to do something, it is told which permission is needed and where to give it.
• Launch from a chat. Your agent can put files live on a website, launch a new website with HTTPS, or set up and update a 6amMart shop from one request.
• Close an app's web installer. A PHP website's Settings has Refused addresses, so a path such as /install answers "not found" once you are done with it.
• More apps work as uploaded. Laravel apps made for shared hosting, Next.js sites with language routing or long security headers, and PHP apps that ship their own packages now deploy and run without changes.
• Smaller fixes. Fewer false alarms on the server overview, a first Laravel deploy migrates its database, new websites answer right away, and the Backups and WordPress pages open faster.
• Security hardening. Several protections were tightened. Updating is recommended.

• Websites and apps, beside your shop. Projects → Create project now offers a static website, a Node.js app, a PHP website, WordPress or Create with AI, next to 6amMart. Each website is kept separate from the others, and nothing about your 6amMart projects changes.
• Static, Node.js and PHP websites. Upload a folder or a ZIP, or deploy from git. Common frameworks are detected and built on the server, a new version goes live only once it answers, and earlier versions are one click away.
• WordPress, managed. One-click install and sign-in to WP Admin, a restore point before every update, plugin and theme management, a page cache that clears when you publish, and sensible hardening from the start.
• Create with AI. Describe a website and Tia writes it in Next.js, builds it and publishes it on your address. Every message is one change you can watch, stop or undo. Bring your own provider from the new AI section.
• Tia, an AI assistant for your server. AI → Tia, or Ask Tia on any page: ask in your own words and she does the work, step by step. Ask mode waits for your approval; anything that cannot be undone always shows you what will run first.
• Automations and AI monitoring. Tia can run checks on a schedule and report by email, Telegram, Slack, Discord or webhook. The panel watches the server every minute, opens and closes incidents by itself, and can explain the cause with AI.
• Connect your own AI agent (MCP). AI → Connect lets Claude Code, Cursor, VS Code and other MCP clients manage the server, with tokens you can limit, expire and revoke.
• Deploy on every git push. Websites deployed from git can deploy themselves from GitHub, GitLab, Gitea or Forgejo, private repositories included.
• Backups and restore for every website. Server backups now include every website, and each website has its own Backups page with Restore. Over SSH: sixpanel backup restore latest --site NAME.
• Two release channels. Settings → Release channel lets you choose Stable (recommended for live sites) or Latest. Every server stays on Stable until you choose otherwise.
• One-click sign-in from AllsWeb. A server ordered from AllsWeb opens its panel from your AllsWeb dashboard with one click. sixpanel sso off switches it off.
• Easier everyday pages. One Projects page for every kind, a full file manager, an Errors tab, phpMyAdmin for website databases, a Domain & HTTPS page that checks each address, and alert email presets for common mail providers.
• Smaller fixes. Updates wait out the system's own package updates instead of failing, the panel's address works on servers with long hostnames, Node.js apps stop cleanly, and several pages open faster.
• Security hardening. Several protections were tightened. Updating is recommended.

Domains and HTTPS

• Adding a root domain adds its www form too. Type example.com and www.example.com is added beside it, with a choice of which spelling visitors are sent to. This works on Domain & SSL and in the create-project and install wizards.
• Fix it from the row that reports it. An address that does not point here yet now has its own "Create the DNS record" or repoint button. A domain already pointing at another server can be moved here, from Domain & SSL or from the install screen.
• Domain status you can trust. A domain on Cloudflare now reads as reaching this server, going somewhere else, or unconfirmed, and only the first gets a tick. www names set up as a CNAME are recognised correctly.
• Every address in your certificate is served over HTTPS. Addresses that had ended up outside it are repaired automatically when the panel starts. Redirects set while a certificate is being issued now take effect straight away.

Installing and updating your shop

• The customer website installs through a wizard. It works like the admin app's wizard and starts from the CodeCanyon zip. Private repositories work over a token or SSH with their own deploy key, and Test connection reads the real branch list before you install.
• Website updates no longer take the live site down. The new version is built beside the live one and switched in only when the build finishes. If a build fails, your live website keeps serving the version it had.
• Installing from a private repository works with the deploy key the panel gives you. "Get the latest code", deploy-on-push and rollback keep working afterwards. If a token is missing, Update the admin app now asks for one on the spot.
• The untouched CodeCanyon download installs end to end. The panel finishes the 6amMart installer for you, and the install record says plainly which way it was done.

Running smoothly

• Addon switches work. Turning an addon on or off in your shop's admin panel now takes effect at once, including Payment & SMS Gateways and Rental. Image uploads in the admin panel work again, too.
• Updates finish, even when something interrupts them. An update stopped by a reboot or by the server's own automatic updates is completed when the panel starts again, instead of being reported as failed. Queue workers and the scheduler always come back after a pause.
• Node.js 26.10.0. SixPanel and your customer website now run on the newest Node.js 26 release, installed for you during the update.
• Server → Health watches compiled-code memory. It shows how full it is, since a full store quietly slows every page.
• A faster, steadier panel. It is back several seconds sooner after a restart and no longer freezes while it sets up a project's cache.
• Your chosen timezone moves the panel's own schedules. Nightly backups, restore tests and certificate renewals now run at the time you expect.
• A project moved to another server stays stopped on the old one, so two copies never run at once.
• Weekly maintenance completes its security updates after updating the panel, rather than skipping them.

Smaller fixes

• Smaller fixes. sixpanel info works on a brand-new server. sixpanel artisan config:cache takes effect immediately. sixpanel db import replaces the database it says it will and tells you plainly whether anything changed. Server security updates repair themselves when the system leaves a package half-installed, and name the package when they cannot. Re-installing after sixpanel server uninstall works, and the first-run setup opens on the step that is genuinely unfinished. The Cloudflare address lists are always on the Firewall tab. Notifications are easier to read, Mac and Windows junk files are removed from uploads, the email-alert form names ports that usually work, and Apply tuning shows its result.
• Security hardening. Several protections were tightened. Updating is recommended.

• "Update this panel" works. Updating the panel from the button, the weekly maintenance window or the command line now finishes properly. From this release on, updates no longer need to be started by hand.
• A fresh server starts clean. It no longer shows a project named after the machine. The Projects link is always in the left menu, including during first-time setup.
• Customer websites from private repositories can be updated. The access token is kept, so "Get the latest code", rollback and automatic deploys work. If you were affected, install the website once more with your token.
• Safer server maintenance. "Update the server's operating system" now previews exactly what a full upgrade will do, including removals. Web server configuration is checked before any reload, so a bad change no longer takes sites down.
• Reliable deploys and restores. "Get the latest code" recovers from an interrupted earlier update, and "Force deploy" now deploys. A restored shop comes back with its storefront and live order updates running. Deleting a project no longer affects another one with a similar name.
• Smaller fixes. "Get HTTPS" sees new DNS records straight away. The Performance page shows the memory settings the database really uses. Backup verification accepts only sensible schedules. The sign-in form no longer clears while you type. sixpanel db info and eleven similar commands say clearly when there is no project yet. A Spanish headline and the light/dark button's language are corrected.
• Security hardening. Several protections were tightened. Updating is recommended.

• Installing from a git repository is guided. Paste the repository address in Install 6ammart Admin and the panel says what it needs, offers to create a deploy key, tests the connection while you watch, and reads the real default branch. Your repository's history is kept, so updates, rollback and deploy-on-push work from day one.
• The address you type is the admin panel's address. Storefront and websocket addresses are added afterwards on Domain & SSL.
• Adding an address sets it up. On Domain & SSL, a new name now gets its DNS record and HTTPS automatically, and the dialog tells you where the domain lives before you press anything. Changing the main address makes your shop answer on it right away.
• Removing an address is clearer. You can choose to remove its Cloudflare record too, and the panel warns when a certificate still lists the name.
• Your credentials stay yours. "Force reinstall" keeps your .env and other protected files, and installs keep your settings out of the code history. Deleting a project cleans up everything that belonged to it.
• A clearer projects page. Each card names the app and release it runs, opens with a normal link, and the grid shows at most two cards per row. Projects deleted into the 7-day grace period keep their scheduled commands, switched off, for a full restore.
• The live log opens when you ask for it, and every "View log" button opens it.
• Smaller fixes. Projects whose name starts with "demo" open normally. Re-installing on a server that hosted a project keeps PHP running, and the first-run timezone step no longer stops it. A restart during a job no longer stops the job. Certificates are matched to the names they cover, and servers without IPv6 no longer fail a working certificate. Deploy keys are named after their project and server, and generating or testing one no longer stalls. An uploaded zip survives a panel restart.
• Security hardening. Several protections were tightened. Updating is recommended.

Bring your shop here and set up in one screen

• Move a running 6amMart shop here from files. Upload the code as a zip or bring it from your git repository, along with your .sql export and your images. Orders, customers, settings and product photos come with it. Find it under Deploys → Put 6amMart on this project.
• The panel reads your upload first. It tells you which 6amMart release the zip holds and asks only for the pieces that are missing.
• Private repositories, two ways. Use an access token, or a read-only deploy key the panel generates for you.
• Creating a project asks for its name. That is all. You can give the web address while the upload is still going. The panel then creates the DNS records and gets HTTPS on the same screen.
• The plain CodeCanyon install finishes on its own. The panel completes the 6amMart installer and hands you a shop that is ready to sign in to. The manual now has a chapter on activation.

New pages

• Activity. One list of everything that has happened on the server, without the panel's own background noise.
• Server → Services. The web server, PHP, the database and each shop's cache, with Restart buttons and live logs. Restarting the web server is now a graceful reload that drops no requests.

Faster and clearer

• Faster cache advice on plain CodeCanyon code. The App .env page now recommends redis there. Measured on one endpoint: 6 database queries per request instead of 53, and 27–30 ms instead of 73–77 ms.
• Pages say one thing at a time. Health, Projects, Deploys, Backups and the disk breakdown lead with the one thing to do next. Tabs show placeholders while loading, and Server → Scheduled shows something in well under a second.
• The panel loads faster on slow connections, especially on a phone on mobile data.
• Seven languages, fully translated. 1705 lines that still showed English in German, Indonesian, French, Portuguese, Spanish, Bengali and Arabic now read in your language.

Fixed

• Backups include every upload. Seller and staff profile photos are now included in every backup and restore.
• Renaming a project's domain updates the whole shop, including the admin panel, live order tracking and the customer website.
• Code updates add the settings a new 6amMart release expects, without touching what your shop already has.
• "No such file or directory" database errors are fixed. Server → Health now has a row for this.
• Smaller fixes. Updates check the panel can start before restarting it. The installer checks free disk space first (6 GB minimum, 12 GB comfortable), prints an address that actually loads, and can be re-run after a failed attempt. Swap survives reboots. Automatic repairs work on servers not set to UTC. "Turn on two-factor" shows its QR code, and sixpanel unlock <address> clears both login locks. Server → Health warns when a server runs more shops than its memory supports. The slow query log turns itself off after 24 hours. Large uploads and deletes no longer freeze the panel, and a stuck database import no longer blocks other jobs.
• Security hardening. Several protections were tightened. Updating is recommended.

• 6amMart version check before install or update. SixPanel supports 6amMart 4.0 and newer, and now tells you up front when code is older, before anything on your site changes.
• Script and version on each project card. Every project now shows what it runs, for example "6amMart 4.1".
• Faster Health page with several tabs open. Open tabs now share one health check. On a busy two-core server a check went from 11.8 seconds to 4.3 seconds, and a slow check no longer leaves the Health tab empty.
• Saving Settings no longer restarts your background workers. Only a real timezone change does anything now.
• Clearer times. Timezones show their current names, and the maintenance window leads with your own timezone and shows both its start and end.
• Clearer alert emails. The email about wrong guesses at your panel address now explains what happened and only suggests a new entry code when it actually helps.
• Security hardening. Several protections were tightened. Updating is recommended.
• Smaller fixes. Health rows that were only slow on the first check after a restart are no longer reported as problems, an amber row now leads with its reason, and the Cloudflare page re-checks your plan's rule limit regularly.

• New: Service memory budget on the Health page. It tells you when your shops together are allowed more memory than the server has, with the numbers and the two real answers: fewer shops or more RAM.
• Cloudflare firewall setup is more dependable. When your site's rule list is nearly full, the panel writes as many rules as fit, the payment-confirmation rule first, and says how many landed. Plans bought through a hosting partner get their full protection, several servers can share one Cloudflare site, and your own rules are left as you wrote them.
• Copying and moving files reports every file. A bulk copy now tries every file and tells you which worked, which did not, and why.
• Weekly maintenance finishes its work. After a panel update during the window, the remaining steps, including operating-system updates, still run.
• Self-repair keeps running. The once-a-minute repair checks are time-limited, and the Health page shows clearly if they ever stop.
• Certificates fit what Cloudflare can secure. The www. name the panel adds is now checked too, and unused certificates are reported again.
• sixpanel domain none reopens the panel on its IP and keeps it open.
• Job logs are readable again. Test results and other ordinary output are no longer blanked out, while passwords still are.
• Temporary logins can deploy and restart services again, as the manual describes.
• Security hardening. Several protections were tightened. Updating is recommended.
• Smaller fixes. Saving one file from two tabs no longer loses work, a long-open tab makes fewer requests, the activity log stays small, a health sentence no longer reads "undefined", and one missing translation was added in all seven languages.

• Config cache problems are now repaired automatically. The issue shown on Health → Config cache safety, which can stop live order tracking while the admin panel looks fine, is now fixed by the panel itself.
• Tabs remember where you are. Settings and Security tabs are now part of the address, so you can bookmark, share or reload them, and only the tab you are looking at does any work.
• Deploys recover better. A failed deploy always starts your shop's background work again, and a stalled code download no longer holds up the nightly backup.
• Installs from untouched CodeCanyon code are more reliable. The shop serves its real pages right after install, a half-finished database import is caught, and repairing an install creates the admin account you asked for.
• Helpful commands. The "deploy failed" email now includes two ready-to-paste commands for your project, sixpanel exec php works on servers with several projects, and sixpanel backup list shows the destination that holds your backups.
• Faster database index check. The nightly check now reads your database layout once instead of after every index.
• Security hardening. Several protections were tightened. Updating is recommended.
• Smaller fixes. The Cloudflare page no longer comes up empty and shows the limits your plan gets, the disk warning now has an all-clear email, the websocket status tells a stopped service from one that keeps restarting, index counts update right after Apply, Server ▸ Info no longer shows "NaN MB", and a false "file changed by hand" warning after enabling Cloudflare-only traffic is cleared.

• The panel now finishes the 6amMart install for you, on untouched CodeCanyon code too. One install sets up the database, your admin account, your business name and the default images. No browser wizard is left to finish.
• New: Finish install. The button on the Deploys page now completes a shop that was left half-installed.
• Server updates no longer get stuck on a half-installed system package. SixPanel finds and finishes it before other work, and names anything it cannot fix safely.
• New install address: installer.allsweb.net/sixpanel/. Running servers keep updating as before, and older saved addresses still work.
• Maintenance page tells the truth. It shows "Ready" only when a window can really run, describes restarts the way your setting is configured, records the restart step, and no longer reports a successful panel update as failed.
• Moves and backups play well together. Scheduled backups no longer pile up, maintenance and moves wait for each other, an interrupted move is recorded as interrupted, and a move stops if the other server cannot finish setting up the site.
• Security hardening. Several protections were tightened. Updating is recommended.
• Smaller fixes. sixpanel ssl status no longer contradicts itself, two quick "Get HTTPS" presses no longer undo each other, failed index builds are shown on the Database page, and database restarts no longer send false worker alerts.

Move to another server

• New: Migration page. Link another SixPanel server under Settings → Server links, then move one project or the whole server from Migration.
• Move everything to a new server. Give SixPanel a fresh server and its SSH login, and it installs itself there and moves every shop, comparing every table and every uploaded file before calling a shop moved.
• Your domain and data stay put until you decide. DNS is never changed and nothing on the old server is deleted, so you can go back at any time. A failed move cleans up after itself so you can simply try again.

New in the panel

• Weekly maintenance window. Settings ▸ Updates and restart can now back up, care for the database, renew certificates, update SixPanel and apply security updates at an hour you pick, with a "Run maintenance now" button.
• Blocked addresses. Security → Blocked addresses shuts an address or range out of the panel at once, and sixpanel block manages the list from the server.
• Monitoring card on Home. Choose the last hour, six hours or 24 hours, and open a per-service usage table.
• Server ▸ Info. Addresses, hardware, operating system and software versions on one page, with one button to copy it all for a support ticket.
• Empty an error log. Logs → App errors → Empty this log clears old entries once you have fixed the cause.
• Choose the panel port at install. Set PANEL_PORT when you run the installer, or change it later with sixpanel port <number>.

Faster and smaller

• Database care removes repeated data. On a real shop with 66,701 orders the database went from 539 MB to 434 MB, 19.5% smaller.
• Faster earning report. From 419–487 ms to 252–336 ms, and from 210 ms to 48 ms for a single month.
• The panel opens faster. About 3.3 seconds instead of 3.8 behind Cloudflare.

Fixes

• Updates and database restarts are quieter. Your app's log no longer fills with errors during an update, and restarting the database no longer sends a false worker alert.
• Security hardening. Several protections were tightened, and the panel now asks search engines not to index it. Updating is recommended.
• Smaller fixes. A stuck backup no longer holds up other jobs, overlapping certificate renewals are no longer reported as failures, an empty backup test is no longer shown as a pass, sixpanel block prints a table again, and each server now gets the build for its own processor type.

• Ubuntu 26.04 LTS and Debian 13 are now supported, and Ubuntu 26.04 is the one to pick. Each installs its own distribution's packages, so security updates arrive with the rest of the system:

Measured on identical servers with the same 66,701-order shop, the speed differences are small, so pick on support length.

• 6amMart runs on PHP 8.5. Tested on both the plain CodeCanyon code and the optimised build.
• Debian 12 is no longer supported. Its security support has ended, and the installer now points you to Debian 13.
• The customer website can be installed before you have a certificate, and it rebuilds by itself once Domain & SSL is finished.
• Smaller fixes. A fresh install no longer shows a false warning about changed files, the panel names Debian correctly, and Node.js is now one stated version for the build and the installer.

• New: Activity page. Everything that happened on the server in one stream, filtered by who, which project and what kind of action, with search and a "View log" button on every job.
• Clearer running jobs. The end of a job is announced by name wherever you are, the live log ends with a clear verdict, and the page no longer jumps to the top when a job starts or ends.
• Busy buttons and new notifications. Every pressed button shows a spinner until the panel answers, and notifications now have a verdict icon, a close button, and stay while you read them.
• Redesigned alert emails. One clean card with a coloured verdict line that reads well in the inbox preview.
• SixPreflight can fix two findings itself: emoji and all-language support in the database, and modules enabled but not installed.
• Better temporary logins and read-only demo. A new temporary login is handed over as three fields with their own Copy buttons, and the read-only demo now shows every page while keeping private values hidden.
• The panel opens faster and in your language. Slow first loads after a restart are gone, the loading screen is never blank, and links from allsweb.com open the panel in your language.
• Faster reports. The item-wise and store-sales reports went from 610–1,060 ms to about 310 ms on our reference shop.
• Smoother updates and deploys. Updates no longer stop on language files the app changes by itself, and push-to-deploy accepts commits that were pushed later.
• Security hardening. Several protections were tightened. Updating is recommended.
• Smaller fixes. Passwords pasted with a trailing space now sign in, the utf8mb4 fix works on the first press, the disk cleanup row shows its real state, and header buttons and icons display correctly.

A running job shows everywhere

• Always know what is running. A pill in the page header names the running job on every page and opens its live log. The page it belongs to shows a progress card that survives a reload or a second tab.
• No more double starts. Buttons that would collide with a running job wait and come back by themselves. A second backup, certificate request or upload is refused with a clear sentence, and a refused upload is turned away in a second instead of after it finishes.
• A successful install now says so, and "Run now" on a scheduled task reports how the run went.

Your database looks after itself

• Speed indexes apply themselves after every install, update, import and restore. Measured on a real shop: the store report went from 151 to 36 ms and the earning report from 180 to 77 ms.
• Nightly database care, nothing to set up. Expired sign-in tokens, old one-time codes and similar leftovers are cleared each night with the shop answering throughout. Your own records are kept until you choose otherwise on the Database page, which shows exactly how many rows each choice removes.

A lighter panel

• Less to read. The check-up folds healthy rows behind a count, the Cloudflare tab only expands what needs you, Backups shows one schedule card, and Home paints in about 90 ms.
• Shops installed from the CodeCanyon zip get a Deploys page that fits them, with the admin password generated for you.
• Setup does more for you. The wizard's last screen turns on daily backups, and weekly disk cleanup is on by default.
• New and reworded text is translated in all eight languages.

Fixes

• Security hardening. Several protections were tightened. Updating is recommended.
• Smaller fixes. Back-to-back certificate requests no longer undo each other, a fresh shop's log stays free of errors while it is still installing, the website zip update asks before going live, the storefront install ends with the right directions, Home shows when the next backup runs, and several check-up false alarms are gone.

SixPanel's new name and logo

• The product is called SixPanel. The panel, manual, command line and alert emails all carry the new name and mark. Your install and update commands are unchanged.

Large CodeCanyon zips upload

• The full 354 MB admin download now uploads. The panel sends it in pieces and reassembles it on the server. Proven on the real download, followed by a clean install of the untouched code.

Two-step sign-in

• The 6-digit code has its own page. Paste the code, space and all, and it submits itself. A wrong code keeps you on the code page, and the new page works on a phone and in all eight languages.

Check-ups that tell the truth

• Live order tracking is checked the way your apps see it, with one button to repair it, and restoring a database fixes it by itself.
• New check-up rows for your customer website, whether alert emails really arrive, failed background jobs, whether your email domain is set up correctly, and the server's own health verdict.
• Clearer messages when a test email cannot get out, when Cloudflare plan limits are reached, or when a login lock trips.

Cloudflare and your server

• Safer Cloudflare switches. Off switches that would have taken a shop offline are gone, website records can no longer be set to "DNS only" by accident, and the panel's rules apply only to your shop's addresses.
• Refuse visitors that skip Cloudflare. A new option, off until you turn it on. If you ever need to lift it, run sixpanel origin-lock off over SSH.
• The Firewall page gives the right advice whether or not your server is behind Cloudflare.

Also in this release

• Restore one project on a server that runs several.
• Storefront builds fit on a 4 GB server with the shop running, and an interrupted build no longer breaks the next one.
• An update warns first when it would sign everyone out.
• If you skipped first-run setup, a Finish setting up button takes you back to it. A new server also starts on its own clock instead of a fixed timezone.
• SixPreflight on your projects now sees your backups and serving settings. Update it from the SixPreflight page in the panel.
• Security hardening. Several protections were tightened. Updating is recommended.
• Smaller fixes. The panel's own certificate renews on a server with no projects yet, private storefront repositories can be installed, restores and updates take effect without a manual step, the "coming soon" page no longer reads as a working site, deploys are filed under the right project, and the language menu no longer marks finished languages as coming soon.

The untouched CodeCanyon download now works end to end

• From zip to a serving shop. If you run 6amMart exactly as it comes from CodeCanyon, the panel now picks the install method your code supports and finishes with the browser wizard when needed, with nothing to re-upload.
• Activate your CodeCanyon licence from the panel. The Deploys page completes activation for the admin panel and the storefront, and activation survives updates, rollbacks and zip uploads.
• Install the storefront from a zip. Upload the website download on the Deploys page and it is built on your server. Until it is ready, visitors see a short "not open yet" page instead of an error.
• Production settings from the start. New installs are set up for a live shop. For a shop that is already installed, open App .env: a banner lists what to change and fixes it in one click.
• Add-on modules look right. Their styles and buttons load on every admin page, including modules you turn on later.

Updates deliver the whole release

• An update now brings everything a fresh install gets, including the sixpanel command line and the server's tuned settings, so an updated server and a new one end up the same.
• Deploys, rollbacks and licence activation take effect straight away on the live site.
• sixpanel version reports the command line's own version.

Backups

• Backups are fixed. After updating, open Backups, press Back up now, then Test my backup now and read the result.
• The "restore everything" button works, and the dialog says what a restore puts back before you confirm.

Also in this release

• Auto-tune agrees with the installer. Settings → Auto-tune no longer suggests changes your server does not need. Measured: extra PHP workers on a small multi-shop server added no throughput and cost memory, so the panel keeps the install's choice.
• Each project has its own cache, so one busy shop never slows another. Updating moves it over without signing anyone out.
• Clearer database clock. The Database page explains when your shop and database disagree on the time and what that affects.
• Security hardening. Several protections were tightened. Updating is recommended.
• Smaller fixes. Daily log rotation for every project, a disk breakdown that adds up and matches across pages, the file manager's Compress button, the dashboard error count, a first page load that now opens in your language, translation fixes in several languages, correct www addresses on Cloudflare domains, a cleaner uninstall, and sixpanel doctor no longer flagging a project that is waiting for its app.

SixPanel without containers

• Runs straight on Ubuntu. SixPanel hosts 6amMart directly on the server with no containers in the running stack, which keeps it quick on a small VPS.
• Several shops on one server. Each project gets its own account, database, background workers and hostnames, kept apart from the others.
• Domains and HTTPS without the guesswork. Type your domain and the panel creates the Cloudflare records (always proxied), issues real certificates and keeps them renewed.
• Install, update and roll back from the panel. Install from git or a zip, preview what an update would change, roll back in one click, or turn on push-to-deploy.
• Backups you can restore. Encrypted snapshots to the server, S3 or SFTP, with a scheduled test restore that proves they work.
• Health checks and alerts. The panel watches your shop, certificates, disk and workers, and emails you when something breaks.
• Your panel on your own domain, with its own certificate.

Faster for signed-in customers

• The app is much faster once a customer signs in. The settings call every app makes on launch now answers in 0.6 ms instead of 16.9 ms, and 27 other shared pages (policies, zones, modules, banners) are served from cache. Anything personal is still built fresh for each customer.
• About 6% faster across the board on servers with 2 GB of memory or more.
• Updates now switch on the speed improvements they bring. If your server is behind its own build, health checks say so and give you the one command that brings it forward.

Also in this release

• The customer manual ships with the panel. All 24 pages are readable in the panel and over SSH, reached from the Help link beside each feature.
• Bot fight mode is your choice. The Cloudflare page explains what it would cost your apps and payment callbacks and leaves the decision to you.
• Security hardening. Several protections were tightened. Updating is recommended.
• Smaller fixes. Shops with several delivery zones always get the right module list, the alerts page shows the address that really receives alerts, the firewall page reads your own certificates before giving advice about port 80, and setting up a live-updates address now creates its DNS record for you.

Development milestone, in testing only. The last of the pre-release rounds: the product was far enough along to be driven end to end on real servers rather than reasoned about, and what remained was proving it behaved the same way twice. This build was never published and nobody received it.

Development milestone, in testing only. The middle of the work, where the parts began to be tested together rather than one at a time. This build was never published and nobody received it.

Development milestone, in testing only. Early development: the shape of the product being settled and the first pieces made to run. This build was never published and nobody received it.