Ready for IT review from day one

SSO, SyteLine roles, your choice of deployment and SOC 2 Type II compliant infrastructure. Written for the IT or ERP manager who approves the project.

✓
Signs in with your SSO · SyteLine roles apply · Every action logged
Ready for IT review from day one
What IT checks first

The same people see the same things they see today

Permissions are enforced when an answer is retrieved, not written into a prompt. When someone leaves and you switch off their account, their access to the AI goes with it.

IT manager

“Where does the layer run, and who holds admin?”

What you see

On-prem, in your own AWS or Azure account, or a dedicated environment we manage. You can change your mind later.

ERP admin

“Can an agent change SyteLine on its own?”

What you see

Agents start read-only, run in your test environment first, and you decide which actions need a person’s sign-off.

The governed gateway

The AI never writes database code

Single sign-on

People sign in with the identity provider you already use. No new passwords, no shared logins.

Least-privilege connectors

Each connector gets only what its workflow needs: specific IDOs, one named mailbox, one document folder.

Your retention rules

You set how long questions, answers and logs are kept. Export them any time.

One switch turns any agent off.

Any agent can be paused without affecting SyteLine or the rest of the layer. Approvals and before-and-after values are logged.

Agents and write-back

Agents start read-only and earn each write permission

Your ERP team will care most about agents that can change SyteLine. Every agent follows the same rules.

Read-only by default

A new agent can look and propose. It cannot change anything.

Two engineers reading charts on a laptop

Proven in your test environment first

Every write workflow runs against your SyteLine test environment before it touches production.

NineTwoThree engineer reviewing work at a laptop with a colleague

A person approves what matters

You decide which actions need sign-off. The approval and the before-and-after values are logged.

Andrew Amann walking a colleague through a screen
Wheels Now
Wheels Now
Case study

Cut order processing from days to minutes with a custom ERP-integrated sales app

70+
A talented team of 70+ experts delivering excellence every day.
150+
Successfully delivered across industries and markets.
98%
Consistently meeting deadlines with precision and reliability.
#1
Leading Boston businesses toward digital success.
Buyer’s guide · 3 pages

What AI to buy, what to own

Four kinds of AI reach a SyteLine shop. When each fits, what you should own, and ten questions to ask.

Buy, run or own

Where Infor’s AI fits, when a tool you already run is enough, and when the AI layer should be yours.

Chatbot or owned layer

What a personal chatbot account can’t do: know your rules, act in SyteLine, or keep your data where you choose.

Six things to own

Your rules, the code and prompts, the record of what the AI did, model choice, training rights and an exit.

Ten questions for any builder

Price, people, SyteLine roles, data, scale, upkeep and ownership, and how NineTwoThree answers each.

FAQs

Questions IT managers ask us

Do you need direct database access to SyteLine?

Not in cloud SyteLine, where Infor doesn’t allow it. We use the ION API Gateway, Mongoose IDOs and the Data Lake. On-prem, we prefer a read replica or IDO calls over direct writes to the database.

Will this slow down SyteLine for our users?

Reads are scheduled and cached for each view, and agents call the same APIs your integrations already use. We agree load limits with your ERP team during validation.

What do you need from IT to start?

A test-environment login with a scoped role, an SSO app registration, and an hour with whoever owns SyteLine security.

How do you keep our shop data secure?

Your data and logs stay inside the boundary you choose: on-prem, your own cloud account, or a dedicated environment. People sign in with your SSO and see only what their SyteLine role allows. Every read and write goes through a governed gateway, agents start read-only, and every action is logged. The infrastructure is SOC 2 Type II compliant, and models run under terms that exclude training on your data.

What happens when Infor ships a new release?

We change nothing inside the SyteLine core, so there’s nothing to re-apply after an upgrade. Cloud SyteLine updates monthly, and we test the layer’s connections against each release in your test environment before it reaches you.

Which SyteLine setups do you work with?

On-prem, single-tenant and CloudSuite.

Other roles

See it from another seat

CEO

Who owns what our AI learns, and what does it cost to find out?

Ownership

Code, prompts and the Shop Map sit in your repo.

Cost to start

60 days of Align and Validate at a fixed price.

Know-how

Your senior people’s rules stay in the company.

Operations

Which orders will ship late, and what should we move?

Late jobs

See a late order while there’s still time to move it.

Morning brief

What changed on your orders overnight, before the shift.

Agents start read-only

You decide which actions need a person’s sign-off.

Contact us

Bring your security questions to our engineers.

Book an hour with our engineers and bring your security questions, or start with a 45-minute Shop Walk on one real workflow.

  • Meet with founders Andrew Amann & Pavel Kirillov

    founders
  • Custom AI implementation roadmap

  • No sales pressure

This site is protected by reCAPTCHA