This is intended behaviour for Next applications. If you're trying to read any variables that isn't non-NEXT_PUBLIC_* on the client, it won't show up. For security reasons, you can only make variables available to Next on the client via NEXT_PUBLIC_*. If you're not getting an env var you set, it might be that you're attempting to read it somewhere on the client instead of on the server (where it would be available; e.g. Next middlewares on app router).

Unfortunately this is specific to the framework you're using (Next) and not the Railway platform, so we're unable to help you out further.

i am only using the var on the decrypt.ts file that i am using the "import 'server-only'", the decrypt i am using in the session.ts that is marked with the 'use server', i am using the getSession function from the session.ts in my page(s).tsx, that all of then are server rendered and passing the user information via props for the client components, i also have a HOC component that wraps all the pages that manage the access to then.. and i checked it is still server rendered

still dont see why i cant use the var without the prefix

and locally it works if i use without the prefix
only the deployed version dont work

Since you are using turbo, please see their docs on this topic -

https://turbo.build/docs/crafting-your-repository/using-environment-variables#environment-modes

You are likely using turbo in Strict Mode.

Fixed it, I forget to put the vars on the "globalEnv".

thanks