Rigsyn

Independent IT consultancy / Öckerö, Sweden

Build it right.
Know where
it can break.

Security consulting, custom software and web development. Practical engineering for the systems your business depends on.

Engagement blueprintScope → delivery
Start with the problem.Requirements · systems · acceptance criteria

Written agreement / defined boundaries

SecurityTest & harden
SoftwareBuild & integrate
WebDesign & develop
Verify. Hand over.Code / docs / findings
Security testing requires the system owner's explicit authorisation. Nothing outside the agreed scope.
Security, software and web — considered together.Clear scope. Documented work. A useful handover.

01 / What Rigsyn does

Three ways
to move forward.

A system to test. A workflow to simplify. A website to build. Start with what you need to change.

Open a service to explore the scope ↘

01

Security consulting

Find the weak points and understand what matters. Get clear findings you can act on, not just a list of alerts.

  • External infrastructure penetration testing
  • Windows application security reviews
  • Anti-cheat and kernel-level hardening
  • Authorised testing and remediation guidance

The handover → Evidence, priorities and remediation guidance.

02

Software development

Make the software fit the work. Custom applications and integrations, with maintainable code and security considered from the start.

  • Desktop applications and internal tools
  • APIs and system integrations
  • Workflow automation
  • Testing, documentation and handover

The handover → Agreed code, tests and documentation.

03

Web development

Give people a clear path through your website. Fast, accessible websites and web applications that work across devices.

  • Company websites and landing pages
  • Custom web applications
  • Responsive interfaces and accessibility
  • Performance and technical SEO

The handover → A tested website and the documentation to maintain it.

02 / From first question to final review

No mystery between
the brief and the handover.

Agree what good looks like before the work starts. Check against it before calling the work finished.

  1. Scope

    We define the problem, the systems involved, deliverables and acceptance criteria.

  2. Agree

    We confirm scope and timing in writing. Security testing requires the system owner's explicit authorisation.

  3. Execute

    We build the agreed solution or carry out security testing, with progress shared along the way.

  4. Verify

    Development is checked against acceptance criteria. Security findings include evidence, priorities and fixes.

  5. Hand over

    You receive the agreed code, documentation or report. Follow-up support and retesting are scoped together.

03 / A firm boundary

Authorised work.
And nothing else.

We only test systems the client owns. If you can't authorise testing of a system, we won't test it.

  • Every engagement has a written agreement.
  • The owner of each system gives explicit authorisation.
  • Nothing outside the agreed scope is tested.
  • Findings are shared only with the client.

04 / Start a conversation

What needs building,
fixing or testing?

Tell us what you're working on and your timeline. We'll reply with next steps and a proposed scope.

contact@rigsyn.dev +46 70 169 97 65

Email or call directly. No form, no extra steps.