Changelog

Nous améliorons constamment nos solutions. Retrouvez ici les dernières mises à jour et nouveautés de Viraza.

Suivez-nous surFacebooketLinkedIn

All changelog posts

product
feature

Lancement du nouveau portail client Viraza

Nous sommes fiers d'annoncer le lancement de notre nouveau portail client, conçu pour vous offrir une expérience de gestion simplifiée.

Nouveau portail client

Nouveautés :

  • Tableau de bord unifié pour suivre l'ensemble de vos services
  • système de ticketing intégré pour le support technique
  • Factures et devis accessibles en un clic
  • Interface responsive et moderne

Ce portail est le fruit de mois de développement et de vos retours. Merci à tous nos clients pour leur précieuse contribution.

product

Dashboard upgrades

The new Projects-first navigation

We've made two upgrades to the Viraza dashboard: a reorganized navigation, and a clearer name for your APIs.

A new navigation

We've reorganized the sidebar so everything in your workspace is in one place. Your projects, keyspaces, ratelimits, logs, and settings are all a click away.

APIs are now Keyspaces (APIs)

We've renamed APIs to Keyspaces (APIs). A keyspace is the container your keys live in, and the new name says exactly that.

  • You'll find your APIs under Keyspaces (APIs) in the sidebar.

  • Your API ID is unchanged, so your integrations keep working. You can continue to use the same api_… value as before, now shown next to the KeySpace ID on each keyspace's settings page.

Read more in the Keyspaces documentation.

Have feedback on these changes? We'd love to hear from you! Email us at info@viraza.net.

feature

Nouveau module de reporting pour Allocation Server

Le module de reporting pour Allocation Server est désormais disponible. Il permet de visualiser en temps réel l'utilisation de vos ressources.

Module de reporting

Fonctionnalités :

  • Graphiques d'utilisation CPU / RAM / stockage
  • Alertes configurables par seuil
  • Export PDF des rapports
  • Historique sur 12 mois

Connectez-vous à votre espace client pour en bénéficier dès maintenant.

security
performance

Mise à jour de sécurité et optimisation SNEN

Nous avons déployé une mise à jour majeure de sécurité pour l'ensemble de la plateforme SNEN.

Correctifs :

  • Renforcement de l'authentification multifacteur
  • Correction de vulnérabilités (CVE-2026-1234, CVE-2026-5678)
  • Optimisation des temps de réponse des API
  • Réduction de 30 % de la consommation mémoire

Nouveautés :

  • Déploiement du module "Vie scolaire" dans 50 établissements pilotes
  • API ouverte pour l'intégration avec les solutions tierces

Cette mise à jour est déployée automatiquement sur l'ensemble des établissements connectés.

product

January Product Update

January was a busy month for the Viraza team. We shipped 47 pull requests across the codebase - from the core API to the dashboard you use every day. We fixed bugs, shipped new features, and shipped a few things we're pretty excited about.

We upgraded the dashboard to Next.js 16 and Zod v4, which significantly improves performance across each page and you should notice this next time you visit.

The identities page now allows you to manage identities just as easily as the API. You can create, update, and delete identities directly from the dashboard. We also removed it from a beta state, making it fully functional and accessible to all users.

identities

Finally we introduced a new members page, which allows you to invite as many members as you need, versus the previous modal which was limited to a single member.

Members Page

Below are the pull requests merged during this month:

Features & Enhancements

  • Enhanced Identity Details Page #4611 - Introduces a comprehensive identity details page for better visibility into identity configurations.
  • New Deployment APIs #4604, #4583 - Adds getDeployment and CreateDeployment to streamline deployment management.
  • Upload URL Generation #4601 - Introduces generateUploadUrl to simplify file upload workflows.
  • Vault as a Service #4555 - Implements vault as a service for improved secrets management and security.
  • Sentinel Secrets Management #4619 - Adds support for sentinel secrets to enhance security controls.
  • Dashboard Invitation Management #4817 - Restricts invitation management to admins for better access control.
  • Redesigned Team Settings #4783 - Redesigns team settings with tabs and invite form for improved user experience.
  • Enhanced Log Details #4774, #4793 - Redesigns log details with v2 improvements and deployment navigation enhancements.
  • Dashboard Alphabetical Sorting #4597 - Sorts log details alphabetically by key for easier navigation.
  • Sentry Integration Controls #4592, #4584 - Adds Sentry initialization controls and structured logging with error filtering.
  • Middleware Error Decoupling #4763 - Refactors middleware error handling for improved reliability and maintainability.
  • Authorization Schema Updates #4816 - Updates authorization schema validation limits for better consistency.
  • Virtualization Hook Updates #4819 - Updates virtualization hook usage for improved dashboard performance.

Bug Fixes

  • IP Logging Fix in API #4829 - Fixes IP logging in the API for accurate request tracking.
  • Roles Null Handling #4833 - Handles null updated_at_m in roles to prevent errors.

Performance Improvements

  • Optimized Key Count Queries #4762 - Optimizes API key count queries with proper COUNT aggregation for better performance.
  • ClickHouse Query Improvements #4609 - Adds configurable request timeout and fixes query issues in ClickHouse integration.

Documentation

  • Documentation Navigation Guide #4838 - Updates "where is stuff?" documentation for better navigation.
  • API Documentation Fixes #4733, #4732, #4731, #4729, #4728 - Fixes various documentation drift issues across multiple packages.
  • Doc Comments for Core Packages #4711, #4710, #4709, #4715, #4714, #4713, #4712 - Adds comprehensive doc comments to pkg/fault, internal/services/usagelimiter, cmd/, pkg/vault, pkg/system_errors, pkg/circuitbreaker, and pkg/proto exports.

product

October Product Update

October was another fantastic month for the Viraza team, with 47 pull requests merged, enhancing features, squashing bugs, and improving the user experience. We also demo'd our new Viraza deploy platform at All Things Open, this has been in the works for a while, and we cannot wait to share more details, and get it into your hands.

Below are the pull requests merged during this month:

Features & Enhancements

  • Context Aware DoWithResult Enhances Robustness #4137 - Introduces context-sensitive methods for improved responsiveness in operations. (Author: @ogzhanolguncu)
  • Unkey Builds for Better Image Building #4098 - Facilitates local and isolated image builds, enhancing the deployment process. (Author: @ogzhanolguncu)
  • Optimization of API Key Handling #4056 - Streamlines CLI interactions by intelligently inferring workspace IDs. (Author: @mcstepp)
  • UI Enhancements for Intuitive User Experience #4060 - Improves user interface elements and keyboard shortcuts. (Author: @ogzhanolguncu)

Bug Fixes

  • Rate Limit Key Enhancement for Accuracy #4200 - Revamps the key format in DurableRateLimiter to reduce errors. (Author: @chronark)
  • Proper IP Whitelist Validations #4063 - Optimizes IP whitelist handling by enhancing string conversion processes. (Author: @Akhileshait)
  • Resolved Identity Deletion Error #4103 - Fixes server error during the deletion of identities. (Author: @Flo4604)
  • Addressed Navigation and State Management in Onboarding #4085 - Reworks the onboarding wizard to prevent duplicate slugs. (Author: @chronark)

Performance Improvements

  • Optimized Rate Limit Counting for Efficiency #4080 - Implements atomic processing for rate limits to prevent incorrect counter adjustments. (Author: @chronark)

Documentation

  • Updated Broken Link in CONTRIBUTING.md #4122 - Fixes a critical 404 error affecting documentation navigation. (Author: @d02ev)

Internal Changes

  • From Keyring to Keyspace: Renaming for Clarity #4126 - Renames several core components to better reflect their functions. (Author: @mcstepp)
  • Container Version Updates Streamline Deployments #4146 - Standardizes container versions across the board for consistency. (Author: @imeyer)
  • GHA Workflows Transitioned to More Reliable Runners #4138 - Migrates GitHub Actions to depot.dev for enhanced operation. (Author: @imeyer)
  • Enhanced Seeder Function Usability #4110 - Refactors test seeder functions for improved type safety and reduced database calls. (Author: @mcstepp)

Testing

  • Comprehensive Testing for IP Whitelist Functionality #4069 - Augments IP whitelist testing to ensure accurate verification and functionality. (Author: @chronark)

Infrastructure

  • Migration of Runners to Depot.Dev #4138 - Shifts infrastructure to leverage new runner technology in deployments. (Author: @imeyer)
  • Infrastructure Overhaul via Removing Obsolete Components #4061 - Cleans out deprecated components to streamline operations. (Author: @chronark)
  • Deployment Application Enhancements #4051 - Focuses on refining deployment processes to elevate operational efficiency. (Author: @ogzhanolguncu)

Security

No security-specific changes were made

product

September Product Update

Summary

September was a busy month for us! We rolled out a slew of new features aimed at Viraza deploy and fixes to enhance user experience and system performance. Key highlights include the introduction of slug routing for workspace scoped dashboard. Plus, we tackled several bugs that were affecting performance and usability. Overall, this month’s updates make the platform more robust and user-friendly, paving the way for future enhancements!

Features

  • New Authentication System: We implemented a simple API key authentication for both CLI and dashboard communication with the control service. #4010
  • Slug Routing: The dashboard now supports workspace-scoped navigation, enhancing user experience. #4009
  • Gateway Logs: Added Gateway Logs to the projects section, providing better insights into deployment activities. #3993
  • Dynamic Data for Demo API: We added dynamic data to the demo API to improve the demo experience. #4002
  • Improved Rate Limits Management: Users can now manage rate limits within the workspace context. #3782

Bug Fixes

  • Fixed Logdrain Crashes: Addressed issues with logdrain that were causing crashes due to changes in the logpush format. #4025
  • Resolved Timeouts: Added timeout handling to prevent unnecessary 500 errors. #4022
  • Corrected Logging Line Locations: Ensured that logging lines are accurately displayed. #3889
  • Fixed UI Inconsistencies: Resolved various UI issues, particularly in rollback dialogs. #3979

Performance Improvements

  • Enhanced Domain Rollbacks: Improved the rollback functionality for domain management, ensuring that users can revert to previous states more seamlessly. #3999
  • Optimized Clickhouse Image: Updated the ClickHouse Docker image to improve functionality and performance. #4033

Refactoring and Chores

  • Domain Refetching: Refactored the system to allow for domain refetching on live deployment changes. #4032
  • Removed Trials: Simplified the subscription system by removing the trial period. #3988
  • Updated Environment Variable Management: Cleaned up the environment variable section in project overviews for better future support. #3946

Documentation

  • Updated API Documentation Link: Corrected the link to the API documentation in the welcome email to ensure users access the latest resources. #3937

Miscellaneous

  • Improved UI for Project Details: A new UI for project details includes active deployment logs and an enhanced environment section. #3853
  • Refined User Experience: Various UI updates, including better button labels and handling of pointer events in components. #3880

Stay tuned for more updates as we continue to refine and enhance your experience with our platform!

product

August Product Update

In August 2025, our team has rolled out a series of improvements aimed at enhancing user experience and application performance. From new UI features for project management to important bug fixes that ensure smoother functionality, we’ve been busy! Key highlights include the launch of a new workspace slug, refined database schemas for demos, and improved error handling. We’re thrilled for you to explore these changes and are committed to making Viraza even better!

Features

  • Enhanced Project Management: A fresh new UI for managing projects and deployments has been introduced, making it easier to navigate and utilize #3797.
  • New Workspace Slug: We've implemented a new workspace slug feature that streamlines workspace identification and management #3849.
  • Improved Gateway Functionality: The gateway routes now utilize VM addresses for more efficient routing #3878.
  • Deployment-Centric API: We've added a new deployment-centric API along with a Get Deployment endpoint #3878.

Bug Fixes

  • Sidebar Improvements: The "load more" functionality has been fixed in the sidebar, allowing users to load additional projects smoothly #3833.
  • Pentest Remediation: Addressed vulnerabilities found during a penetration test, ensuring user roles and invites are securely managed #3885.
  • Curl Example Update: Updated the curl example to utilize the V2 endpoint #3832.
  • Key Redaction: Improved key redaction to ensure all keys are properly handled and redacted #3860.
  • Scrollability Fix: Fixed an issue where the workspace creation wizard was locked on smaller screens, now allowing scrollability #3843.
  • Workspace ID Query Fix: Resolved slow queries by ensuring that the workspace ID is correctly queried #3836.

Performance

  • Database Schema Enhancements: We’ve made database schema updates that enhance performance and efficiency for our demo environments #3878.
  • Redis Usage Limiting: Transitioned to a Redis-based usage limiter for improved latency and tracking #3800.

Documentation

  • Updated Docs: Documentation has been refreshed to reflect changes in API structures and endpoint versions, ensuring clarity for all users #3747 and #3712.
  • RFC for Let's Encrypt: Introduced an RFC outlining the architecture for issuing TLS certificates for custom domains #3754.

CI Improvements

  • Enhanced CI/CD Pipelines: Optimized CI workflows, including the removal of outdated steps, to streamline our continuous integration processes #3709.
  • Upgrade Scripts: Added utility scripts for environment migrations and improved configuration management #3748.

We hope these updates enhance your experience with Viraza. As always, your feedback is invaluable to us!

product

July Product Update

July was an action-packed month for Viraza, with a whopping 172 pull requests merged. Key highlights include significant improvements in API error handling, UI enhancements for permission management, and a streamlined deployment process. We also focused on performance tweaks, especially with our database interactions and CI workflows. With thorough documentation updates, our users can better navigate the new features and fixes. Dive in to see the highlights of what we achieved this month.

Features

Bug Fixes

Performance

Documentation

Chores

product

June Product Update

Major Enhancements and Fixes in June 2025

This month has been all about enhancements and refactoring! We've moved several components into the UI for better organization and streamlined workflows. The introduction of new features like optional permission slugs and encryption during key creation adds flexibility. Bug fixes have improved the overall stability of the application, addressing issues like Stripe integration and spacing inconsistencies. Our ongoing commitment to improving the user experience shines through this month's updates!

Features

Bug Fixes

Refactoring

Chores

Documentation

Dependencies

Thanks for your continued support and contributions! Let's keep building together!

product

April Product Update

Create Key Wizard

Key Creation Wizard

Our Create Key wizard just got better! Enjoy these new and improved features:

  • Instant feedback during key creation
  • Apply multiple rate limits per key
  • Easy-to-use JSON formatter for metadata
  • Clear warning about one-time key display
Key Creation Wizard with error

API Settings Update

Our new API Settings screen is designed for intuitive control over your API configurations. Adjust default bytes, prefixes, and manage security settings seamlessly.

API Settings

Roles Returned as Part of verifyKey

The /v1/keys.verifyKey endpoint has been updated to include a list of roles associated with the key in the verification response, enabling applications to easily determine the user's roles during key verification and make more informed authorization decisions. This simplifies role-based access control implementation and requires one less API request.

Seeding Local Development

We have introduced proper seeding for log pages and metrics, enhancing the ability to generate realistic test data and improving the development and testing experience. You can easily seed a workspace by running pnpm local and selecting Seed Clickhouse/DB. Our CLI will then ask a series of questions about what you would like to seed and how much test data you want.

Seed example

Other PRs

Bug Fixes

  • #3189: Tooltip now shows the correct time interval
  • #3115: Improve keyboard combinations
  • #3187: Ensure charts and logs data count match
  • #3157: Ensure username doesn't overflow sidebar
  • #3118: Show timestamp correctly on click
  • #3119: Usage chart colors and fix layout shift issue
  • #3104: Only allow access membership list fetching to current org context.
  • #3099: Prevent cancellations if the org has multiple members
  • #3094: Improve errors when using natural language searches
  • #3080: Make confirmation dialog trigger correctly on workspace members page.
  • #3079: Pagination issue and improve fetch logic
  • #3037: navbar-popover active state
  • #3055: Use only time as cursor
  • #3054: Query clickhouse by time

Documentation

  • #3173: Explain how delete protection works

Other Changes

  • #3191: Prevent revalidation of logs and charts to improve dashboard performance.

product

March Product Update

New Features

Pricing Updates

While this isn't a new feature, we've made some updates to our pricing plans to better serve everyone whether you are just starting out or scaling a project.

  • Larger Free Tier : We've significantly increased our free tier! You now get 150,000 requests per month completely free, up from the original 2,500. This allows you to thoroughly test Viraza and start scaling your project before entering your credit card.

  • Simplified Pricing : We've streamlined our pricing model to focus solely on requests. We've removed the separate charges for key verifications and standalone rate limit verifications, making it much simpler to understand and predict your costs.

  • Tiered Pricing : We're introducing tiered pricing starting at just $25. This gives you more flexibility to choose the plan that best fits your needs as you scale, we also reduced the price significantly, below is an example of 10M requests in a month on the new and old pricing:

Old PriceNew Price
$1010.00$250.00
  • No Overage Charges : We will no longer charge for overages. If you exceed your monthly request limit, we won't charge you but send you an email congratulating your success. If you continue to exceed the tier every month, we will ask you to upgrade to the next tier.

We believe these changes will make Viraza an even more attractive and accessible solution for developers of all sizes and allow you to scale without worrying about your bill.

Check out the updated pricing table on our pricing page here.

Ratelimit / API Overview overhaul

We have completely revamped our ratelimit and API overview page, making analytics the main focus of the page.

Ratelimit

You can see all the important details about a specific namespace, including:

  • Request count
  • Identifier
  • Passed / block requests
  • Last request
Ratelimits example

You can also override an identifier directly on the page to make blocking or allowing requests more easily.

Override example

API

In the API overview, we provide all the important details about a specific API, including:

  • API request totals
  • Active key totals
  • Valid / Invalid requests counts and types
  • Last used details

We also include a natural language search and filter to allow you to quickly analyze and manage your API data.

API Overview example

You can also see important details about a specific key, but clicking on the key will open a modal with more information.

Key Details example

Other PRs

Changed

  • Sidebar component added with improved UI and accessibility features.
  • Global baseUrl function created to infer Vercel URL for WorkOS redirect more reliably.
  • Sampling support for tracing allows specifying the rate via configurations.
  • Updated layout.tsx to improve URL structure and maintain consistency.

Removed

  • Removed outdated and redundant quota checks.
  • Unused files and code related to the unused banner component.

Fixed

  • OAuth extraction from URL to improve security.
  • Dark mode forced on the auth page to show correct colors on dialogs
  • Vercel redirection configuration for WorkOS fixed to handle edge cases.
  • Timestamp conversion for logs and related elements.
  • Layout shifts, missing props for UI components, and hydration issues addressed with dynamic imports and better coding practices.
  • Multiple minor bug fixes like navbar realignment, format issues, wrong environment variables, and outdated quota handling.

Security

  • Addresses a critical security vulnerability, CVE-2025-29927.

product

January Product Update

New Features

Logs (Beta)

Our new reques logs are designed to simplify your debugging experience. With comprehensive request filtering, real-time monitoring, and intuitive natural language processing, managing API requests has never been easier.

Logs example
  • Comprehensive Request Filtering: Now you can view all API requests, including those that encountered errors. Easily filter these requests by status code, method, and path to quickly identify and troubleshoot issues, ensuring a smoother development process.

  • Natural Language Filtering: Say goodbye to complex, time-consuming filtering! Our new natural language processing feature allows you to filter API requests using simple, conversational phrases. Just type what you’re looking for, and let our system do the rest!

  • Live Logs for Real-Time Monitoring: Turn on live logs to watch your logs in real time, making it easier to see if your latest deployment is working as expected.

  • Request IDs for Streamlined Support: Each API request provides you with a request ID. This enhancement simplifies the support process—just share the request ID with our support team, and we can quickly locate and address your concerns.

Improvements

Standalone Rate Limit Logs: We took everything we built in the request logs and replaced the old rate limit logs, so you can see all the important details in one place, including the timestamp of the request, identifier, status, when the rate limit resets, and more.

Rate limit logs example

Migrating Keys Now Accepts an External ID: You can now migrate keys using the external ID ready to be used with our identity product; just pass in the external_id while migrating the key.

Permanent Key Deletion: You can now permanently delete a key. By default, Viraza has the ability to recover a key if requested, but by passing "permanent": true with your deletion request, you can bypass this recovery option.

Default Prefix and Bytes: The API will now use the default bytes and prefix set by the user if they aren't included when creating a key.

Top Bugs Crushed

product

December 5th Changelog

Official Python SDK

We now have an official Python SDK that is developer-friendly & type-safe, making it as easy as possible to start with your favorite language. You can get started right away by installing our package pip install unkey.py

Below is an example of how to create a key using the new SDK:

import os
import unkey
from unkey_py import Viraza

s = Unkey(
    bearer_auth=os.getenv("UNKEY_BEARER_AUTH", ""),
)

res = s.keys.create(request={
    "api_id": "api_123",
    "name": "my key",
    "external_id": "team_123",
    "meta": {
        "billingTier": "PRO",
        "trialEnds": "2023-06-16T17:16:37.161Z",
    },
    "roles": [
        "admin",
        "finance",
    ],
    "permissions": [
        "domains.create_record",
        "say_hello",
    ],
    "expires": 1623869797161,
    "remaining": 1000,
    "refill": {
        "interval": unkey.CreateKeyInterval.DAILY,
        "amount": 100,
    },
    "ratelimit": {
        "limit": 10,
        "type": unkey.CreateKeyType.FAST,
        "duration": 60000,
    },
    "enabled": False,
})

if res.object is not None:
    # handle response
    pass

I want to thank Jonxslays for his community SDK, which allowed developers to get started immediately and provided Viraza with the unkey.py name.

Identities

Until today, you had the option to assign an owner to your keys, allowing you to filter keys by a specific owner. This was useful for fetching keys by user or organization via the API, but it didn't provide any additional functionality.

With Identities, you can now group keys together and share metadata and rate limits across them.

For example, we have a company named ACME Corp, which has the enterprise tier and access to our GPT-4o wrapper, with a per-day token limit. So first, we create the identity with the limits:

curl --request POST \
  --url https://api.viraza.net/v1/identities.createIdentity \
  --header 'Authorization: Bearer unkey_root_key' \
  --header 'Content-Type: application/json' \
  --data '{
  "ratelimits": [
    {
      "name": "enterprise_tier",
      "limit": 50000,
      "duration": 3600000
    },
    {
      "name": "tokens",
      "limit": 86400000,
      "duration": 10
    }
  ],
  "externalId": "acme_corp"
}'

Now we have an identity, we can attach it to one or many keys by referencing the external_id:

curl --request POST \
  --url https://api.viraza.net/v1/keys.createKey \
  --header 'Authorization: Bearer unkey_root_key' \
  --header 'Content-Type: application/json' \
  --data '{
  "externalId": "acme_corp",
  "apiId": "api_123",
  "byteLength": 16
}'

Finally, when we verify a key, we will deny the request if one of the rate limits is exceeded. You can read more about the identity product and use cases in our documentation

WHOAMI

A new endpoint has been introduced to allow you to retrieve details about any API key when the key ID is unavailable. Users can send the actual API key to /v1/keys.whoami, which will return the associated data. This is a great way to verify remaining usage, current limits, or identities associated with a key.

curl --request POST \
  --url https://api.viraza.net/v1/keys.whoami \
  --header 'Authorization: Bearer unkey_root_key' \
  --header 'Content-Type: application/json' \
  --data '{"key": "sk_123"}'

The API will return details about the key:

{
  "id": "key_123",
  "name": "API Key 1",
  "remaining": 1000,
  "identity": {
    "id": "id_123",
    "externalId": "ext123"
  },
  "meta": {
    "role": "admin",
    "plan": "premium"
  },
  "createdAt": 1620000000000,
  "enabled": true,
  "environment": "production"
}

Ratelimit Overrides

When we introduced standalone ratelimiting, we included a feature allowing custom overrides without needing to deploy user code. This feature was originally only available via the Viraza dashboard. This month, we introduced the ability to create, update, delete, and list overrides via our API; this unlocks the ability to integrate this into support tooling or back office tools.

curl --request POST \
  --url https://api.viraza.net/v1/ratelimits.setOverride \
  --header 'Authorization: Bearer unkey-root-key' \
  --header 'Content-Type: application/json' \
  --data '{
    "namespaceName": "email.outbound",
    "identifier": "user_123",
    "limit": 10,
    "duration": 60000,
    "async": true
}'

You can see how to implement them into your tooling in our API reference.

Content

product

July 26 2024 Changelog

For the past two weeks, the team has been laser-focused on tackling technical debt, improving our documentation, and crushing UI bugs.

Unkey Turso Cache store

We collaborated with the team at Turso to introduce a new cache-store. This cache store allows using embedded replicas or remote Turso DB. You can read about implementing your cache store in our documentation.

Documentation improvements

Our documentation has been getting some serious improvements in the past month. First, we introduced a new layout that provides a better way to find what you are looking for based on your use case.

We also introduced new getting started guides that can help you get started with ratelimiting or with identities

We also wrote a new guide on ratelimiting your One Time Passcodes for DDOS and bot protection.

Improvements

  • Double-clicking a root key now redirects to settings PR

  • Optimize all images on our landing page PR

  • Add flags to pnpm local PR

  • Removed contentlayer and added content collections PR

  • Root key details overhaul PR

Bug Fixes

  • Create role modal breaks if the permissions name is too long PR

  • Delete permission modal breaks if the permissions name is too long PR

product

July 14 2024 Changelog

After Accelerate our first-ever launch week, where we launched products like Toolbox, vault, and LLM caching. We are now working on improving infrastructure, usability, and our docs.

Permissions and Roles

We introduced Authorization into beta at the beginning of the year. This week we introduced them into the API to allow you to create and manage them easily.

Creating a role

You can create a role by passing the name and description, the name can be anything you want it to be, make sure your root key has rbac.*.create_role

curl --request POST \
  --url https://api.viraza.net/v1/permissions.createRole \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "name": "dns.records.manager",
  "description": "dns.records.manager can read and write dns records for our domains."
}'

Creating a permission

You can create a permission by passing the name and description, the name can be anything you want it to be, make sure your root key has rbac.*.create_permission

curl --request POST \
  --url https://api.viraza.net/v1/permissions.createPermission \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "name": "record.write",
  "description": "record.write can create new dns records for our domains."
}'

You can find the rest of the endpoints for managing roles and permissions in our documentation

Attaching permissions or roles to a key

You can attach a permission or roles via the API to do this you need to provide the permission or role id to the keys.addPermissions or keys.addRoles.

Add Permission

curl --request POST \
  --url https://api.viraza.net/v1/keys.addPermissions \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "keyId": "<string>",
  "permissions": [
    {
      "id": "<string>"
    }
  ]
}'

Add Roles

curl --request POST \
  --url https://api.viraza.net/v1/keys.addRoles \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "keyId": "<string>",
  "roles": [
    {
      "id": "<string>"
    }
  ]
}'

You can find the rest of the endpoints for managing roles and permissions on a key our documentation

You still need to attach your permissions to roles or directly to a key via the UI but we will add the endpoints in the coming weeks.

LLM Semantic Cache onboarding

If you are a fan of LLM's and want to use Viraza's Semantic caching when you sign up and create a gateway in a single click. This will allow you to save money and reduce latency for your users.

Onboarding

Bug fixes

  • Fix UI Caching issue when deleting keys Link to PR

  • Add missing permissions to root keys in the dashboard Link to PR

  • Filter out deleted keys from permissionsLink to PR

Docs improvements

documentation
community

May 2024 Changelog

Documentation refresh

We have updated our documentation to provide more detailed information on how to use Viraza. Our goal is to make it easier for you to get started and find the information you need. We hope you find the new documentation helpful. If you have any feedback or suggestions, please let us know.

Viraza Local Development

We have dramatically improved our local development experience. With Viraza Local Development, you can now develop and contribute to Viraza without the need for Planetscale and other dependencies. This feature is perfect for developers who want to contribute to Viraza.

Check out our documentation to learn more about Viraza Local Development.

Migrating to Viraza

We added a new API endpoint that allows you to migrate your existing keys to Viraza. This allows for zero down time migration and makes it easy to handle large key migrations. You can find more information in our documentation.

Go SDK

We now have official support for Go through out SDK, you can find all the documentation here.

Improvements

  • Added support to delete all keys in an API docs

Fixes

  • Fixed a bug where root keys were not being deleted properly PR
  • Fixed ratelimit property name PR
  • Added updatedAt property to keys PR

product
company

April 2024 Changelog

A new look

Viraza has a new look! We have updated our website to provide a more modern and hand crafted feel. Our team spent countless hours designing and developing the new site. We hope you enjoy it as much as we do!

A new domain

With the launch of the new website, we have also moved to a new domain. You can now find us at unkey.com. We always wanted to have a .com domain, and we are excited to finally have it.

A new team member

We are excited to welcome a new team member to Viraza. Rodz has joined us as a design engineer. He will be working on new features and improving the dashboard to be more user friendly and intuitive.

Unlimited Keys on pro plan

When you upgrade to the pro plan, you now have unlimited keys. This means you can create as many keys as you need without worrying about hitting a limit. We hope this change makes it easier for you to manage your keys and use Viraza to its full potential.

Fixes

  • Fixed a bug where banners would overlap if more than one was displayed at the same time PR
  • Correctly display payment method on the dashboard PR

Content

product

March 2024 Changelog

Standalone ratelimiting

We are introducing standalone ratelimiting. With this feature, you can rate limit anything while still leveraging the power of Viraza. Our ratelimiting feature works similarly to our keys, providing low global latency and detailed analytics. Moreover, you can configure overrides for specific identifiers, giving you more flexibility.

You can check out a demo that shows our synchronous and asynchronous implementation versus a Redis-based ratelimiter.

Bug fixes

  • Fixed a bug where the byte size was not correctly used when creating a key from the dashboard commit

Content

product

Authorization Alpha Release

Authorization through RBAC

We are excited to announce the Alpha release of our Authorization offering. This feature is opt-in and is available to all customers; while it is in Alpha, we advise keeping it to development environments.

Create roles

When creating roles, we wanted to give you the ability to provide them with an intuitive name and a description. This allows others in your organization to understand the purpose of the role and also gives you the ability to match the systems you have in place.

Create Role

If you have permissions created already, you can assign them to your roles during the creation process. If you don't have permissions created yet, you can create them after creating your role and assign them later.

Creating permissions

Our permissions are designed to be flexible; you can create permissions specific to a single API or service, or you can create more general permissions that can be used across multiple roles. We also offer the ability to wild card your permissions for more flexibility.

Create Permission

After you have created your permissions, you can assign them to your roles.

Visualizing roles and permissions

Viraza has always focused on making securing your APIs more accessible than ever. With the introduction of our Authorization offering, we wanted to simplify how you can see what roles and permissions are assigned to a key and update them as needed.

Roles and Permissions

Permission details

If you want to understand which roles are using permission, when it was last used, what keys are attached, and when it was last updated, you can do so by clicking on the permission.

Permission Details

Create key UI updates

The team refined our create key UI to provide a better User experience. The new UI offers toggles for enabling features while ensuring you are provided with actionable feedback when there is an error.

Create Key UI example

Content Roundup

How to build and authenticate an AI API using Modal, Neon, and Viraza

If you want to learn how to use Neon Postgres and Modal to build, host, and deploy an OpenAI Whisper API - fully secured by Viraza. We collaborated with the team at Neon team to create a tutorial that walks you through the process. You can find the tutorial here.

Decoding CLI Auth

Command Line Interfaces (CLI) have become integral tools for developers looking to streamline their workflows, but how does CLI authentication work? In our latest blog post, we break down the process of authenticating a CLI tool and how Viraza can help. You can find the blog post here.

Prêt à transformer votre entreprise avec le digital ? Contactez-nous dès aujourd'hui pour un audit gratuit de vos besoins IT.

Contactez-nous