Changelog

Platform updates

What changed on Zenifra, newest first.

View documentation
  1. Applications

    Logs page: search across every project

    The new Logs page, in the console menu, searches at once the logs of every application in the organization with Log history on, over the last 7 days: type a text or a request_id and filter by project, instance, version and output. JSON logs show up formatted, with the colored level and the message, and one click shows every field; in Raw, lines show up as they arrived. Sort by time, with milliseconds, hide columns and export up to 2,000 lines as CSV or JSON. Lines reach the search in about 20 seconds. Searching, filtering and exporting have no cost: logs are charged only for the space the history takes in Storage. In the project logs card, the Recent tab gained a Time column and also shows the instances that have already ended.

  2. Storage

    Storage is out of beta

    Storage is available to every organization. The limits of up to 10 buckets, 50 GB stored and files of up to 20 GB are now the default limits per organization. Need more? Contact support. Transfer to the internet is free until Dec 20, 2026 and, from Dec 21, 2026, costs R$ 0.80 per GB. Traffic between Storage and applications on Zenifra stays free. Storage and request prices and free allowances do not change.

  3. Storage

    Storage open to every organization

    Any organization can now create its own Storage in the Console, with no request or invitation: open Storage from the menu, create your Storage and your first bucket. Storage is still in beta, with the same limits per organization (up to 10 buckets, 50 GB stored and files of up to 20 GB; contact support for more) and the same price: R$ 0.18 per GB-month, with the first 5 GB free, and transfer to the internet free during the beta. To use Log history, which requires Storage, you now just need to create it.

  4. Applications

    Log history in Armazém

    Keep your HTTP application logs to read later, even when an instance is recreated. Turn on Log history in the project settings and choose to keep it for 7, 30 or 90 days. Every hour, logs are compressed and saved to a bucket in your organization's Armazém, and files older than the retention are deleted automatically. In the new History tab of the logs card, pick the day and hour, search for text and download the file for that hour. Files are billed as Armazém storage and count toward the free 5 GB, with no extra fee. Requires Armazém, which is in beta.

  5. Integrations

    Visual panels in the MCP

    In clients that support MCP Apps, such as Claude and ChatGPT, the Zenifra MCP now shows visual panels next to the answer: organization overview, project list, metrics, builds, latest failed build, AI usage and project incidents. Panels follow the app theme and language and open the project in the console with one click. RabbitMQ Queues can now also be filtered in the MCP project list.

  6. Deploy

    Deploy to Zenifra button

    Add the Deploy to Zenifra button to your open source project README. The link opens the Console with project creation already filled in: a public image or a public Git repository by URL, from GitHub, GitLab or another Git server, with port, runtime, commands and environment variables. Whoever clicks does not need to connect their Git provider account; someone without an account signs up and comes straight back to the form, reviews everything and creates the project in their own organization. Projects from a public repository are updated with a manual deploy. The documentation shows how to build the link and includes the badge in English and Portuguese.

  7. Deploy

    Deploy from GitLab

    Connect your GitLab account on the Account page and create projects by picking one of your repositories, including those in subgroups. Each person connects their own account, and only they use that connection. With Auto-deploy on, every push to the branch publishes a new version. On paid plans, every merge request gets a Preview environment, and Zenifra keeps a single comment on the merge request with the preview address and lifetime, updated until the preview ends. If your institution runs its own GitLab, the organization owner connects the instance with a token.

  8. Organizations

    Zenifra for Education and each person's own GitHub

    Colleges can now have the Education area, separate from the organization's Standard area: classrooms with professors and students, students' projects isolated from the institution's projects and a separate invoice, marked as Education, with a subtotal per classroom. Switch areas in the organization selector, under Type: Standard | Education. The Education area is activated by the Zenifra team at the college's request. And each person can now use their own GitHub in each organization: once you connect yours, you only see and use your own repositories there; without it, the organization GitHub connected by the owner still applies.

  9. Applications

    Project visitors, with real latency

    See who visits your application and how it responds on the new Visitors page of the project: unique visitors, page views, countries, referrers, browsers, systems and how much of the traffic is robots, split by kind. Real latency shows how long each visitor waits for the response, from their network to the application, and the routes table brings the real latency, the application time and the error rate of each route. Response status, response time and data volume complete the page, with a period of 1 hour, 24 hours or 7 days. No script to install and no cookies: everything comes from the requests that reach the project. History goes from 1 to 7 days, depending on the plan.

  10. AI

    Yearly AI plans

    AI plans per member can now be yearly: you pay 11 months and use 12. Choose Monthly or Yearly when assigning the plan. The whole year goes on the organization's next invoice and lasts 12 months; an upgrade bills only the difference prorated to the rest of the year, and the Seats tab shows when each plan renews.

  11. AI

    AI plans per member

    Give each member of the organization an AI plan with a fixed monthly price: Lite (R$ 20), Standard (R$ 71.90) or Premium (R$ 323.90). Each member gets their own API key, compatible with the OpenAI SDK and tools like opencode, with every model in the catalog and usage that resets every week (from Lite to Standard, also every 5 hours), with no per-token charges. In AI models, the Plans tab shows the usage of each window, the last use of the key and the requests of the last month; the member can generate a new key at any time. The plan goes on the organization invoice, prorated by day in the first cycle.

  12. Databases

    Database connections with no tweaks and configurable TLS

    The PostgreSQL URI now ends with sslmode=require and connects with TLS in any common driver, such as node-postgres, Prisma, asyncpg, psycopg, PDO, and Go, with no code change. TLS stays on by default, and you can turn it off and back on at any time in the database TLS card, for drivers that do not use TLS. For MariaDB, the Connection panel has the ready string, with TLS, for each driver: mysql2, mariadb, Prisma, SQLAlchemy, and Go.

  13. Jobs

    Change the plan and command of scheduled Jobs

    Change the plan and the command of a scheduled Job after creating it, without recreating the Job. Under Edit, the Job plan card lists the plans with their price per minute and, on Jobs that run a Docker image, the Run command card overrides the image command and arguments, without a new build. Changes apply from the next run; a run in progress finishes as it was.

  14. Organizations

    Teams ready for classes and groups

    New in Teams. Under Project visibility, choose that each member sees and operates only the projects they created, with no access to the projects, logs and variables of their teammates. Under Plans allowed for members, set which plans members can use in the team projects. And with the Join link, bring a whole class with a single link, with validity, a usage limit and, optionally, only for emails from a verified domain of the organization. Each member can also connect their own GitHub under Account and pick My GitHub when creating projects, to use their own repositories. For now, the organization GitHub stays the default in organizations.

  15. Organizations

    Project limits and sign-in times in Teams

    Set how many projects a team can have and how many each member can create in it. Team maintainers see when each person signed in to Zenifra, with the date and time of each recent sign-in, and the owner sees the same for the whole organization on the Members page. To turn off the team projects at a set time, the documentation shows how to do it with a scheduled Job.

  16. Organizations

    Teams that own projects

    Group people in your organization into teams, such as Backend or Marketing, and put projects in the team: team members see and operate those projects, with no per-project access to manage. Pick the team when creating a project, move projects between teams and filter the project list by team. Whoever leaves the team loses access right away.

  17. Databases

    RabbitMQ in Queues

    Create Queues with managed RabbitMQ®: exchanges, routing keys, acknowledgements, dead-lettering and scheduled delivery, with the same prices as the paid Queues plans. On the Basic, Premium and Enterprise plans, the queue runs on 3 highly available nodes and changes plan from the console, keeping stored queues and messages.

  18. Billing

    From the free plan to a paid plan, without recreating

    A Free project or a PostgreSQL on db-free can now move to a paid plan from the console, with the Move to a paid plan button, keeping its address, variables and data. The confirmation shows the hourly price and what the plan costs per month, hourly billing starts at the change and the free period is never billed. After the change, you cannot go back to the free plan.

  19. Databases

    Free PostgreSQL with more CPU and memory

    PostgreSQL on the db-free plan now has 0.3 vCPU and 256 MB of RAM, the same resources as db-starter, and stays free.

  20. Applications

    Errors of the last 24 hours on the Dashboard

    The Dashboard now has an Errors (24 h) card and an Apps with errors in the last 24 hours list. For each application, database or Job with a problem, you see what happened (out of memory, unexpected stop, image download failure, failed build, failing health check or failed Job run), the last time it happened and how many times, with a shortcut to open the project. The history stays visible after a new deploy or a plan change.

  21. Applications

    Why an instance restarted

    When an instance of an application, PostgreSQL or MariaDB database restarts or is replaced, the console shows the reason for the last 24 hours: the plan memory ran out, an unexpected stop or the temporary storage was exceeded, with the time and the number of restarts. If it was memory, you know you need to reduce usage or change plans.

  22. Deploy

    PHP straight from the repository

    Deploy PHP 8.3, 8.4, and 8.5 applications, such as Laravel and Symfony, from GitHub or Forgejo, with no Dockerfile to maintain. Zenifra installs the Composer dependencies and the extensions composer.json requires, and serves the app with FrankenPHP.

  23. Databases

    Storage usage on every plan

    The Storage card of databases shows used space on any plan, not only from db-premium, and warns when usage goes above 80% and when storage is almost full. With email alerts on, you get one notice at 80% and another at 95%, without repeats until usage goes down.

  24. Templates

    Templates with multiple databases

    A template can now create up to 5 managed databases with the application, such as PostgreSQL for data and ClickHouse Analytics for reports. On the Customize page, every database is created in the same operation and each connection variable is filled by the right database, including the Analytics HTTPS URL.

  25. AI

    Kev decision model in the AI API

    Kev, an open model (Apache-2.0) built to answer questions instead of generating text, is now in the catalog as zenifra/kev-4b. Send a text and choice, yes/no, and score questions to POST /v1/systemone and get the probability of each answer back in about 150 ms. Billing is in reais: R$ 0.2244 per million input tokens, with free output.

  26. Deploy

    Go and Java straight from the repository

    Deploy Go (1.25 to 1.27) and Java (17, 21, and 25, with Maven or Gradle) applications from GitHub or Forgejo, with no Dockerfile to maintain. Zenifra compiles during the build with the command you set and starts the binary or the jar.

  27. Storage

    Public files in Storage

    Everything in Storage is still private by default. Now you choose which files are public, when uploading or later from the file details, and you can make them private again at any time. Each public file gets a fixed address at <bucket>.armazem.zenifra.com, for images and files of your site or app. Buckets and the file list are never public.

  28. Deploy

    Git repository section for every GitHub project

    For any application deployed from GitHub, change the repository, branch, runtime, and version in the console, in the Git repository section, along with the commands, root directory, and deployment mode. Before, GitHub projects created in the console only let you change the commands and the deployment mode.

  29. Billing

    Replace your card from the console

    Replace the organization card on the Billing page with Replace card, without contacting support. The new card is used for upcoming charges and the previous one leaves the organization; if the new card is declined, the previous one stays saved.

  30. Organizations

    24-hour invite link

    Invite someone without knowing their email: generate a single-use link, valid for 24 hours, on the Members page. The person creates the account with just a name, email and password, and it belongs only to your organization, with no organization of its own and no sign-up credit.

  31. Deploy

    Faster GitHub deployments

    Deployments from GitHub are now faster: your application can be live in about 30 seconds.

  32. Organizations

    Join through the email domain

    Verify your company email domain in the organization with a TXT record. Anyone who creates an account with an email from that domain is invited, right after signing up, to join the organization as a member, with no permissions until you grant them.

  33. Storage

    Storage in beta

    Keep images, videos, backups and other application files in Brazil, in private buckets with an industry-standard API. Upload and download from the Console, share files with 7-day links and create access keys limited to buckets and networks. Billing is in Brazilian reais, by the hour, with 5 GB free. Ask to join the beta from the Console.

  34. Integrations

    Storage in the CLI and MCP

    The Zenifra CLI gained the zenifra storage commands for buckets, files, access keys and usage, and the zenifra database group, which works for every managed database. MCP now lists Storage, its buckets and files, read only.

  35. Databases

    Automatic backups for managed databases

    PostgreSQL, MariaDB, ClickHouse, Key-Value and Queues now have automatic backups included in the plan at no extra cost: 1 to 3 backups per day, kept from 3 days up to a month depending on the plan. To restore a backup, contact support by WhatsApp or email.

  36. Applications

    Storage alerts and alerts for databases

    Email alerts now warn you when storage reaches 80% of its capacity, persistent or not, and also cover PostgreSQL, MariaDB, ClickHouse and Valkey, with restarts, CPU, memory and storage. The alerts card in the console lists exactly which emails you get.

  37. Databases

    More storage for Key-Value and Queues

    Increase storage for Key-Value databases and Queues from the console, starting from each plan minimum.

  38. Databases

    Optional public access for managed databases

    Turn off public access for PostgreSQL, MariaDB, ClickHouse, and Valkey and reach the database only through private connections between applications in your organization. When you turn it back on, the address and port stay the same.

  39. Applications

    Warning when the image cannot be downloaded

    When the application image does not exist, is private without credentials or its registry does not respond, the console shows the reason and what to do, and the project shows as unavailable instead of running. Public images with a missing name or tag are refused right at creation and on image changes.

  40. Preview

    Preview link on the pull request

    When the automatic preview of a new GitHub pull request is ready, Zenifra comments once on the pull request with the environment address and lifetime.

  41. Databases

    ClickHouse plan changes

    Move ClickHouse to a larger or smaller analytics plan from the console, without recreating the database.

  42. Organizations

    API key editing and expiration notices

    Edit the name, expiration and allowed IPs of organization API keys, see who created each key and get an email a month before it expires.

  43. Jobs

    Jobs from GitHub

    Create scheduled Jobs straight from a GitHub repository, with Node.js, Python or Bun and a task command, in addition to Docker images.

  44. Deploy

    Tags and releases when connecting a repository

    Choose By Tag or By Release deploys when connecting a GitHub repository to an existing project. In these modes, New build publishes the latest version that matches the pattern.

  45. Applications

    Private connections

    Connect applications and Jobs to other applications, PostgreSQL, MariaDB, ClickHouse and Valkey in the same organization through an internal address, without exposing anything to the internet.

  46. Deploy

    Faster builds and smaller applications

    Builds from the repository start faster, reuse dependencies and steps that did not change between deployments, and produce smaller applications.

  47. Deploy

    Version switches without dropping traffic

    When you publish a new version, the previous one keeps serving while the new one starts, including applications that take a few seconds to boot.

  48. Applications

    Logs on every plan

    Follow application logs in the console on any plan, including Free. Metrics remain available according to the plan.

  49. Deploy

    Root directory for monorepos

    In GitHub and Forgejo projects, choose the repository folder where install, build, and start run, and publish each application in a monorepo as its own project.

  50. Jobs

    Scheduled Jobs

    Run recurring routines from a Docker image with a cron expression in UTC, follow each run in the console, and pay only for the minutes the task ran, in Brazilian reais.

  51. Applications

    Email alerts for applications

    Turn on email notices when an instance restarts or stops unexpectedly, or when CPU or memory usage reaches 80% of the plan.

  52. Deploy

    Bun, Node.js 26, and Python 3.14

    Deploy straight from the repository with Bun, plus Node.js 20 to 26 and Python 3.11 to 3.14, with no Dockerfile to maintain.

  53. Deploy

    Deploy from Forgejo

    Connect a Forgejo instance, including one hosted by your organization, and publish the application manually or on every push to a branch, tag, or release, with a preview environment for each pull request.

  54. Deploy

    Deploy from GitHub tags and releases

    GitHub projects can publish from tags and releases that match the configured pattern, in addition to push deployments on the branch.

  55. Preview

    Native previews for GitHub pull requests

    Each pull request to the chosen branch can get a Preview environment with no workflow, API key, or image in the repository. The preview is removed when the pull request closes.

  56. Databases

    Managed ClickHouse for analytics

    New ClickHouse plans with HTTPS client connections and usage metrics in the console.

  57. AI

    Custom names for AI keys

    Name your AI keys to identify each integration in the console.

  58. AI

    Model catalog with capabilities and BRL prices

    The public model catalog shows context window, capabilities, and prices in Brazilian reais.

  59. Integrations

    OAuth access for the CLI and MCP

    The Zenifra CLI and MCP clients can connect to your account with OAuth, without copying keys by hand.

  60. Domains

    Three-character primary domains

    Projects can use primary addresses with only three characters.

  61. Templates

    Official Templates catalog

    n8n, Metabase, WordPress, and other ready-to-run applications are available in a public catalog, with one-click deploys.

  62. Applications

    Optional HTTP healthchecks

    On eligible plans, configure a check route, follow failures, and let the platform recover instances automatically.

  63. Databases

    Native database metrics

    Managed databases now show engine-specific metrics, including PostgreSQL query latency.

  64. Databases

    Stable addresses for managed databases

    PostgreSQL and MariaDB now use a stable connection address dedicated to each database.

  65. Preview

    Preview environments

    Create temporary environments from GitHub projects or container images and validate changes before updating the main application.

  66. Databases

    Managed Valkey

    Valkey with Key-value, Cache, and Queue profiles, secure connections, credential rotation, and a free plan.

  67. Account

    Account language and website in English

    Set your account preferred language and browse the website in Portuguese or English.

  68. Templates

    Templates with databases

    Templates can declare the database they need and create the application and a compatible database in one operation.

We respect your privacy

We use essential cookies to run this site. Measurement and marketing cookies, such as Google Ads, are only enabled when you accept all cookies. Read our cookie policy.