Skip to content

NSIEnterprise

Decision governance across every location you run.

One Decision Record per decision, one named owner and an outcome verified against evidence, in every location. Written for the operations and finance leaders who approve a vendor before the first call.

Record
One per decision
Owner
One named person
Outcome
Verified against evidence
Languages
English, Spanish, Portuguese

Built for

Operators with more than one site, and the people who sign off.

The method comes from intelligence analysis, not from project management. Every Decision Record carries graded sources, a stated confidence and a named key assumption, following the ICD 203 analytic standards, and a verdict is written only when the evidence supports it. Read the analytic standards →

Multi-location service operators

Regional companies running crews, service appointments or branches that need the same decision standard in every location, with one record per decision wherever it was made.

Operations and finance leadership

Leaders who need to see what was decided, who owned it, what waiting would have cost and whether the decision paid, without reading every system themselves.

Procurement and security review

Teams that need written answers, a data map and plainly stated limits before a signature. Where a control does not exist yet, this site says so.

What is live today

Live

Controls you can test before you sign.

Everything in this list is in production now. Each item links to the page where you can check it yourself.

  1. 01

    Signed decision receipts

    Every verified outcome can carry a North Star Verified receipt, signed with Ed25519 and chained so that nothing sealed can be altered. Anyone can check a receipt on the public verification page without trusting us.

    Check it →
  2. 02

    Per-system connection keys

    Each attached system gets its own key, stored only as a hash and revocable one at a time. The priority score is always computed on our side, so no sender can set its own.

    Check it →
  3. 03

    Public API and agent access

    Any system that sends JSON can file a decision, and a Model Context Protocol server lets AI agents score, submit and verify the same way. Nothing is approved or verified by the agent itself.

    Check it →
  4. 04

    Decision templates

    A standard owner, deadline rule and rating ranges per account, so decisions arriving from connected systems are completed consistently and every filled field is visible on the record.

  5. 05

    Two-factor sign-in enforced by the database

    Any account can add an authenticator app. Once enrolled, the database refuses privileged reads from a session that has not presented the code, not only the screens.

  6. 06

    Account privacy by design

    Customer decisions, demand data and systems are private to each account under row-level access controls. Not even North Star's owner can read them.

    Check it →
  7. 07

    Export and erasure

    A customer exports or deletes its own account. Erasure removes every owned row in one transaction and keeps only sealed public receipts and payment records, and it reports both.

    Check it →
  8. 08

    Append-only history

    Every change to a Decision Record appends a dated snapshot, so corrections keep the prior evidence and nothing is silently rewritten.

  9. 09

    Monitoring and incident records

    Scheduled jobs, server errors and browser errors are recorded with no personal data. A health watch runs every ten minutes, opens an incident when something stops, and the public status page shows the current state.

    Check it →
  10. 10

    Three languages on every page

    English, US Spanish and Brazilian Portuguese on every public page. A decision keeps its language from the record to the verified outcome, and signed bytes never change with the language shown.

Security and data handling

Plain statements, including the ones that say not yet.

In transit
Served over HTTPS with strict transport security, a nonce-based content security policy and frame protection on every response.
At rest
Records live in a managed database in a United States region. Connection keys for attached systems are stored encrypted and account keys only as hashes.
Access
Row-level access controls on every table a browser can reach, least-privilege grants re-applied daily, and two-factor sign-in enforced by the database once enrolled.
Attestation
No SOC 2, ISO 27001, HIPAA or PCI attestation is held today, and none is claimed. Ask about a specific control and you will get a direct answer about whether it exists.

The full statement of what is collected, who processes it, how long it is kept and how to make it go away lives on the trust page. Read the trust page →

On the roadmap

Planned, not available

What larger deployments usually ask for next.

None of these is available today. Ask about any of them and you will get a direct answer about where it stands. Nothing on this list is a commitment or a date.

  • Single sign-on

    Sign-in through your identity provider.

  • Roles and permissions

    Viewer, owner and administrator roles inside one account.

  • Organization hierarchy

    Organization, region and location, with records rolled up at each level.

  • Administrator console

    Central settings, templates and keys for every location.

  • Audit log export

    Every change, by whom and when, delivered for your own retention.

  • Outbound webhooks

    Notify your systems when a record changes.

  • Published uptime commitment

    A written availability target backed by the status history.

  • Standard data processing terms

    Data processing and master agreement templates ready for review.

How an engagement works

Four steps, each one checkable.

  1. 01

    Scoping conversation

    Your locations, the systems you run and the decisions that matter most this quarter.

  2. 02

    Written security answers

    Your questionnaire answered in writing, with the data map and the limits stated above.

  3. 03

    Pilot at one location

    One real decision, one owner and one verified outcome before any wider rollout.

  4. 04

    Written agreement and rollout

    Enterprise terms are set in the written agreement and locations are added as agreed. Nothing is billed before it is signed.

Plan rates are shown to signed-in clients. Enterprise terms, additional locations and any custom control are set in the written agreement.

North Star Intelligence LLC, a Utah limited liability company operating as North Star Intel. Items marked planned are not available and are not commitments. Nothing on this page forms a contract, and no service is provided until an agreement is signed.

Enterprise

Start with one location and one real decision.

Tell us how many locations you run and which systems they use. We confirm scope, security answers and a pilot before anything is signed.