Skip to content

What's new

Improvements and new features across the panel and the agent, newest first.

  1. Lowering retention asks for the second factor, and the post-backup command warns when it fails

    • Lowering the minimum retention, shortening or removing a retention tier, or turning off one of the safeguards now requires the owner and the authenticator code — the same protection as permanent deletion. Raising protection stays free.
    • The minimum retention no longer accepts tiers shorter than itself, nor going above the permanent deletion period.
    • Agent 0.4.1: when the post-backup command fails, the backup shows as completed with a warning, and the command's output comes along (before, it stayed only on the server). Folders excluded from the plan are no longer walked, and changing the key of a second agent on the same machine uses that agent's configuration.
  2. Agent 0.4.0, referrals in plain sight, and retention that keeps what you asked for

    • When you create the organization, the panel shows whether you arrived through a partner's link and who they are, with the option to decline the referral.
    • A scheduled permanent deletion takes effect after the 14-day grace period, and the other owners and administrators get an email notice when it is scheduled.
    • Minimum retention now also keeps the version that was still current within the period, and canceled or suspended accounts no longer have versions deleted by the automatic cleanup.
    • Agent 0.4.0: reinstalling or updating on Linux restarts the service right away (before, the old process kept running); restores of files in cold storage no longer hold up the queue; when every file fails, the panel shows the cause; on macOS, the panel shows the right command to restart an agent installed without sudo.
  3. Agent 0.3.9: restores with original permissions and dates, and reinstalls that just work

    • A restored file comes back with the permissions and owner of the file it replaced, and with the modification date from the backup (before, it was readable only by the administrator and dated at restore time).
    • A bucket without versioning no longer passes as a completed backup: the session fails and tells you to turn versioning on, which is what makes point-in-time restore possible. A backup where some files couldn't be read shows the reason and the first file that failed.
    • Reinstalling the agent with a new code now uses the server and storage of the new code (before, the old configuration could leave it unable to talk to the panel). Several agents on the same machine no longer erase each other's identity when uninstalling.
    • The agent renews its credential with the panel on its own before it expires, honors HTTPS_PROXY, and shows empty folders in the folder browser.
    • Panel error messages are translated on every server, plan and storage screen, and so are the retention policy rules.
  4. Agent 0.3.8: OneDrive on Windows, files in use, and the site in three languages

    • Agent 0.3.8, Windows: OneDrive files downloaded to the computer are now backed up (before, Desktop and Documents redirected to OneDrive came out empty). Cloud-only files are left out, so the backup doesn't download the whole OneDrive. The agent's token and key are now readable only by administrators, and the service writes a log to C:\etc\arkame\agent.log.
    • Agent 0.3.8: a file changed while it is being uploaded no longer enters the catalog with content different from what was recorded — it fails in that run and uploads in the next. A folder without read permission leaves the backup partial instead of "complete". Files over 156 GB now upload, and stopping the service mid-backup no longer leaves the session stuck "running".
    • Restore: the file tree shows every folder (it used to cut off at 5,000 files without warning), and Docs/ and docs/ no longer mix. The cart says why a restore was refused.
    • The overview chart and dates follow your time zone. With a scheduled cancellation, "Next invoice" shows when the subscription ends.
    • The site and documentation are now available in English (arkame.app/en) and Spanish (arkame.app/es).
  5. Sign in by email, schedules that hold, and alerts when a backup fails

    • Besides a Google account, you can sign in with a link sent to your email. The link is valid for 15 minutes and works only once. You don't need a Google account to use Arkame.
    • Fix: the plan schedule was not being respected — a daily plan could run every time the agent checked in. Now it runs at the chosen time, in the time zone of whoever set it up, including cron schedules. Editing a plan's name no longer changes the next backup.
    • A backup that failed or finished incomplete is now reported by email, at most once per plan per day, with what the agent reported. You can turn it off in Settings → Organization → Email notifications. If the account is suspended (trial expired without a subscription, or overdue payment), you also get an email saying backups are paused and restore keeps working.
    • Docker is the recommended installation on Linux servers, and the Docker command now also restores. On Windows 11 with Smart App Control on, the installer without code signing is blocked, and the panel warns you; on Windows 10 and Windows Server, it works.
    • Cloudflare R2 is removed from the list of new storages: it doesn't offer versioning through the S3 API, and restore by date depends on the old versions. Existing R2 storages keep working. Oracle Cloud buckets with uppercase letters or underscores are now accepted as they are.
  6. Windows servers: folders, paths and restore in Windows format

    • In the backup plan for a Windows server, the folder browser starts at the drives (C:, D:…) and paths follow the Windows format, such as C:\Users\Maria\Documents. Restore suggests C:\Restaurados and puts each file back on the right drive.
    • Fix: a plan with a Windows path could end as "completed" without copying any file. Now a folder that can't be opened makes the backup fail with the reason, and the plan's other folders carry on.
    • Fix: the before and after backup commands were not saved when creating or editing the plan. Now they are.
  7. Installing the agent is a single command, and the bucket key is tested first

    • On Windows, press Windows + R, paste the command the panel shows and press Enter: the installer asks for administrator permission on its own. You no longer need to open PowerShell as administrator. On Linux, macOS and Docker, it's also a single command — on Docker, the same command registers the server and leaves the agent running.
    • The installer asks for the bucket access key and secret and tests them against the bucket before registering the server. A wrong key is rejected right away, with the reason — before, the installation went ahead and the first backup failed without warning. The key still stays only on your server.
    • Each server has its own connection status with the bucket: if one of them has the wrong key, the panel shows which one, even if another server uses the same bucket with the right key.
  8. Billing in reais, and the partner program as it actually works

    • Organizations in Brazil now pay in reais: R$ 25 per server per month, with no IOF tax on international purchases. Outside Brazil, it stays US$ 5. The currency is decided by the organization's country, given at sign-up.
    • The free trial really ends: once the 14 days are over without a subscription, scheduled backup stops — as the end-of-trial notice always said. Restore keeps working, because the files are yours and are in your bucket.
    • Correction of something we announced in September: the automatic split of the payment between Arkame and the reseller partner, and the commission payout through Stripe, never actually worked. Reselling is now wholesale — the partner subscribes and pays the wholesale price for the whole customer base and bills their own customers with their own invoice —, and the referral commission is paid by PIX in Brazil or by international transfer elsewhere, against an invoice.
  9. The overdue alert now knows your plan

    • The "backup overdue" alert in the panel used a fixed 26-hour window, whatever the plan's schedule. Now it uses the schedule: an hourly plan alerts after three hours, not twenty-six; a plan that runs once a week only alerts after the week is up.
    • If you only have manual plans, you no longer see the alert. There was no schedule to fall behind, and the alert lit up anyway and never went away.
    • If you pass the storage connection test, you also stop seeing the "the agent did not respond" alert when your computer's clock is ahead — the time calculation is now done by the server.
  10. Guided installation and the panel in your language

    • Installing the first server became a five-step walkthrough, with the credentials written by a command that doesn't leave the key in the terminal history, and the screen waiting for the server to show up.
    • Numbers, sizes, dates, durations and money now follow your language: "1,2 GB" and "US$ 27,50" in Portuguese, "1.2 GB" and "$27.50" in English. Before, both conventions appeared on the same line.
    • Error messages in Portuguese, Spanish and English, saying what happened and what to do — instead of the internal code that showed up before.
    • Fix in the provider comparison: Google Cloud Storage and OCI no longer appear with Object Lock. Both have their own retention, but not through the S3 API, which is how the Arkame agent talks to the bucket — the lock can't be configured that way.
  11. Database backup, done right

    • Plans now have commands before and after the backup: generate the dump with pg_dump, mysqldump or mongodump and protect the resulting file — copying the files of a running database saves something that won't restore.
    • If the command fails, the backup is canceled instead of keeping the previous day's dump. The command output shows up in the session, so you can find out why without logging into the server.
    • Applying to the partner program is now a form, with a queue and status tracking, instead of an email.
  12. Subscription available and the panel in Portuguese

    • You can subscribe from the panel: US$ 5 per protected server per month, by card, charged only for what is in use.
    • The partner tier follows the size of the customer base: it goes up as soon as the volume justifies it and only goes down after two consecutive months below the band.
    • No more jargon: in Portuguese, "agent" became "servidor", "storage" became "armazenamento", "tenant" became "organização", and the same goes for restore, job, log and signal. In English and Spanish, each in its own language.
    • You choose which notices you get by email, in Settings → Organization. The declined-payment notice can't be turned off — without it, an account could be suspended without anyone knowing the card failed.
  13. Partner area and the business accounts

    • Recurring commission calculated every month, on the first day, on the closed month. It first offsets your own subscription and the rest accrues until the minimum payout amount — the statement shows what was generated, what became credit, what has already been paid and the balance that hasn't reached the minimum yet.
    • Partner branding in the panel: customers of a partner now see the partner's name, logo and color. Custom domain not yet — the panel stays at save.arkame.app.
    • Partners can now track their own customer base: customers, servers, failing backups and revenue generated — without reaching data from other partners' customers, which is enforced by the database and not just by the screen.
    • Referral link for partners: whoever arrives through arkame.app/r/<your-name> is marked as your referral, and the attribution counts when the organization is created — even if that's weeks later.
  14. Restores and History in a single view

    • Restores and History became a single view, with filters by type, period, status and server kept in the address — you can reload, go back and send the link to whoever is helping.
  15. What the product promises, the product does

    • The retention policy now runs: the cleanup the screen described now happens, with the plan recorded before any removal and a limit per round.
    • A suspended account now blocks new backups — and restore stays available, because someone with an overdue payment can't be left without their own data.
    • Isolation between organizations reinforced in the database itself, in addition to the application.
    • Each agent's credential now requires proof of possession of the key.
    • Two-step verification in the panel, with recovery codes.
  16. Per-server billing and email notices

    • The subscription is now per protected server, not a fixed amount — it grows and shrinks with what you use.
    • Real invoices in the panel, with history and receipt.
    • Email notices for failing backups, offline agents and the end of the trial period, in the language chosen for the account.
    • Support, refund policy and contact pages.
  17. Website live and installable agent

    • arkame.app published, with a waitlist for the first spots.
    • Agent v0.1.0 available for Linux and Windows, installed with a single command line.
    • Daily backup of the platform database, with verified restore.
  18. Panel experience improvements

    • Restore hub with Explore (folder tree) and Timeline (points in time) modes, plus search.
    • Real-time tracking of restores, step by step.
    • On-demand connection test: the agent validates credentials and measures the bucket's used size.
    • Notifications in the panel (pending agents, failed backups and restores).
    • Backups-per-day chart and data-transferred card on the overview.
  19. Agent validated end to end (OCI + AWS)

    • Backup and restore validated against real buckets on OCI and AWS S3, with integrity verification (SHA-256).
    • Multipart upload and download for large files.
  20. Panel live

    • save.arkame.app in production with Google sign-in.
    • Agent registration (Docker or binary), BYOS storages and backup plans.
    • Smart retention policy per storage.
What's new · Arkame