Help center

Security boundaries

Code-substantiated review and change-control boundaries.

#

Adding user accounts and login to your app

If your app needs people to sign up and log in, OCNexus can build that in. Secure user accounts are one of the standard pieces it includes, so your customers can create an account, log in, and have their own space in your app.

Just mention it when you describe your app — "people need to sign up and log in", or "each customer should see only their own data" — and OCNexus sets it up. Sign-in is built to be secure from the start, so the information your users trust you with is protected.

You can also add it later. If your app does not have logins yet and you decide you need them, just ask, and OCNexus will add accounts to your existing app.

#

How the Forge keeps your code safe

The Forge never pushes changes directly to your main branch. Every change it makes happens on its own separate branch first, exactly the way a careful engineer on your team would work.

Once a fix is ready, the Forge opens it as a pull request so you can see exactly what would change before it goes anywhere near your live code. Your main branch stays untouched until you decide to merge.

Because nothing lands without your review, you are always able to say no, ask for changes, or simply leave a pull request unmerged. Your production code is never at risk of an unreviewed change slipping in.

#

Improving or fixing an app you already have

OCNexus does not only build new apps from scratch — it can also work on an app you already have. Connect your project, and OCNexus can review it for bugs, security issues, and rough edges, then fix what it finds.

This is useful when something is not working right, when you want a health-check on an existing app, or when you just want it improved. OCNexus looks through the app, tells you in plain language what it found, and can go ahead and fix the issues for you.

You stay in control of what gets changed. Review the findings, decide what you want fixed, and OCNexus handles the work — the same way it does for a brand new build.

#

Signing in and fixing sign-in problems

OCNexus uses your GitHub account to sign in. That means there is no separate OCNexus password to create, remember, or reset — you log in with GitHub, and GitHub handles the password.

If you cannot sign in, work through these in order: - Make sure you are signed in to GitHub in the same browser. - Confirm you are using the same GitHub account you originally signed up with. If you have more than one GitHub account, it is easy to land on the wrong one. - If you forgot your GitHub password, reset it on GitHub directly — OCNexus cannot reset it for you because it is not an OCNexus password. - If you signed in before and it suddenly stops working, OCNexus may need you to re-approve access to GitHub. See "Connecting your GitHub account".

If you have tried these and still cannot get in, contact support and we will help you get back into your account.

#

What the Forge looks for in your code

Think of the Forge as a careful second pair of eyes on your codebase, watching for the kinds of problems that tend to cause trouble later if nobody catches them early.

In plain terms, it looks for things like: reliability risks — code that could break under real-world use; security issues, such as a secret key accidentally left in the code or a spot where bad input could sneak through and cause harm; files that have grown so large they are hard to safely change; error handling that quietly hides a problem instead of surfacing it; and dependencies that are not pinned to a specific, tested version, which can cause your app to behave differently without warning.

Today the Forge understands JavaScript/TypeScript and Python codebases, with more languages planned over time (see "Which repositories can I connect to the Forge?"). Whatever it finds, it explains in plain language — you decide what matters and what gets fixed.