--- title: "Buckets, AI Magic Config, Restricted Environments, and more" date: 2025-11-28 number: 0266 url: https://railway.com/changelog/2025-11-28-buckets-ga --- # Buckets, AI Magic Config, Restricted Environments, and more Happy Thanksgiving to those celebrating! 🦃 We've got something to be thankful for — Buckets are now generally available! No more reaching for third-party storage solutions; Railway's got you covered. This week we're shipping Buckets for everyone, expanding Magic Config with AI-powered intelligence, introducing Restricted Environments for teams with strict security requirements, updating our Template Kickback program, and shipping CLI improvements that make linking services and checking deployment status a breeze. Let's get into it! 🚄 ## Buckets [Video: Buckets are now available on all plans] After weeks of battle-testing in Priority Boarding, Object Storage is ready for prime time. Buckets are now **generally available** — S3-compatible storage that lives right alongside your services on Railway. No more juggling credentials from external storage providers, just `cmd+k` in your project canvas, Choose “+ New service” and then select **Bucket**, choose a region and you're ready to store files. Here's what you need to know about pricing: **Free Plan** Buckets are available on the Free plan with sensible limits to get you started. You get 50GB while on the 30 day free trial, after that you you can store up to 10 GB. Perfect for side projects, prototypes, and learning the ropes. **Pricing structure** - **No egress fees** — Download as much as you need without worrying about surprise charges - **No per-operation costs** — We don't nickel-and-dime you for every PUT, GET, or LIST request - **Pay for storage** — Simple, predictable pricing based on what you store. $0.015 per GB-month **Account limits** - Hobby plan: you can create up to 50 buckets and store up to 1TB across your workspace - Pro plan: you can create up to 100 buckets, with no limit on the amount of data you can store - Enterprise: custom limits and pricing **Private by Default** Buckets serve private files only. Your data stays secure, and you control access through your services. If you need public file serving, deploy a public proxy service to handle that layer — giving you full control over caching, access patterns, and CDN configuration. **Buckets in Templates** We shipped [Buckets in Templates](https://railway.com/changelog/2025-11-07-notifications) a few weeks back and Template creators can include storage-backed resources that deploy cleanly in one click. When someone deploys your template, Railway automatically provisions the bucket and wires up credentials to the services that need them. Ready to hack on Buckets? [Check out the documentation](https://docs.railway.com/guides/storage-buckets), and let us know what you build in [Central Station](https://station.railway.com/) or by [tagging us on X](https://x.com/railway). ## Magic Config Gets Smarter — Now Powered by AI [Video: Magic Config now detects docker-compose files and suggests project structure] Magic Config continues to evolve. After launching [last month](https://railway.com/changelog/2025-10-24-magic-config#magic-config-to-priority-boarding), we've been shipping improvements that make service configuration even more seamless. Here's what's new[ in Priority Boarding.](https://railway.com/account/feature-flags) **Docker-Compose Detection** Connect a repo with a `docker-compose.yml` file, and Railway will now use it to scaffold your entire project. Under the hood, we're now using AI to make this even smarter: - **Project Name Suggestion **— Analyzes your README, `package.json`, and other config files to suggest a meaningful project name - **Domain Setup Agent** — Determines if a service should be publicly accessible and adds a domain if needed - **Service Connections ** — Sets up reference variables between services (e.g., connecting your backend to a database URL) We'll also: - Build & deploy the necessary services and databases automatically - Pull variables from your code and give them initial values or set generator functions This is another step toward Railway understanding your application and configuring everything automatically. Connect your repo, and let Magic Config handle the setup. Try it out in Priority Boarding and share your feedback in [Central Station](https://station.railway.com/). ## Restricted Environments [Image: New for Enterprise: ] For teams with strict security requirements, not everyone should have access to production. Restricted Environments let you lock down sensitive environments so that non-admin members can see they exist but cannot access their resources — variables, logs, metrics, services, or configurations. The key detail: Workspace members who have the “Member” and “Deployer**” can still trigger deployments via git push**. This means your CI/CD pipelines keep working, but engineers without admin access can't peek at production secrets or logs. This builds on the [Role-Based Access Control](https://docs.railway.com/reference/teams#inviting-members) (RBAC) Railway gives you: - **Admin** — Full administration of the workspace and all projects - **Member** — Access to all workspace projects with the ability to create and configure services, but can't delete or manage workspace settings - **Deployer** — View projects and trigger deployments through GitHub, but can't access logs, variables, or configuration Restricted Environments add another layer of control for your most sensitive workloads. To enable Restricted Environments for your Enterprise workspace, [contact us](https://railway.com/enterprise#enterprise-calendar-embed). Once enabled, go to **Project Settings → Environments** and toggle the **Restricted** switch for any environment you want to lock down. We're actively working on even more granular controls. What would you like to see? Let us know in [this Central Station thread](https://station.railway.com/feedback/feedback-rbac-on-railway-6e729188). ## Template Kickback Program Updates [Video: Templates now have dedicated support sections on Central Station] If you're not familiar, the [Template Kickback program](https://railway.com/open-source-kickback) lets you earn money when users deploy your templates. You get 25% of what Railway makes from template deployments — no limits, no minimum amount required. [Cash withdrawals](https://railway.com/workspace/earnings) are available in $100–$10,000 increments via Stripe Connect. Here's the thing: templates require maintenance. Minor patches, security updates, and sometimes major upgrades that require template updates. Great templates need ongoing care, and we want to incentivize that. To do that, we're restructuring how the 25% cut is distributed: - **15%** from template usage (when users deploy and run your template) - **10%** for answering questions about your template This brings balance to the template ecosystem. Users can deploy templates with confidence knowing the creator is incentivized to provide support, and creators are rewarded for maintaining and supporting their work — not just for the initial publish. [Central Station](https://station.railway.com/my-template-queue) now has a dedicated section for templates. A [queue of questions](https://station.railway.com/my-template-queue) users have asked about your templates will be displayed, and you can earn that additional 10% by helping them out. Railway partners also now get dedicated pages where you can view all Railway templates that’s using their project. [Image: View all templates that are using a Railway Partner’s technology] Here are a couple that just launched: - [Prisma](https://railway.com/deploy/storage/prisma) - [Drizzle](https://railway.com/deploy/storage/drizzle) - [Directus](https://railway.com/deploy/cms/directus) ## Better CLI Service Commands [Video: The Railway CLI now has dedicated service subcommands] The [Railway CLI](https://docs.railway.com/reference/cli-api) just got a quality-of-life upgrade with new subcommands for the `railway service` command: 1. `railway service link [service] `Link a service to your current project. `railway service ` still works and redirects to `link`. 2. `railway service status` - Check deployment status for your services with color-coded output: Status output includes service name, deployment ID, and color-coded status: - 🟢 Green for `SUCCESS` - 🔴 Red for `FAILED` or `CRASHED` - 🟡 Yellow for `STOPPED` or `SLEEPING` - 🔵 Blue for in-progress states like `BUILDING` or `DEPLOYING` This makes it easier to script deployment checks in CI/CD pipelines or quickly see what's running across your environment. Thank you [@anonrose](https://github.com/anonrose) for the contribution! ## Fixes and Improvements - We improved [cron job](https://docs.railway.com/reference/cron-jobs) timing accuracy. Previously, scheduled jobs could occasionally run late. Now, cron executions are punctual and consistent.