Yea. $29 per month, per 5k users if you are using SaaS

but we plan on having tiered pricing.. similar to how gitlab's pricing works.

any other issues with Okta apart from their pricing?

no

cool. thanks

how can i run it with my website?Can you help me with the steps.

please follow the quick setup guide: https://supertokens.io/docs/emailpassword/quick-setup/overview There is a video tutorial as well (in the above links).

I have been trying to migrate to Prisma from TypeORM and I get this issue when trying to sign up

Can you check the logs?

If u r using docker, try docker logs

You might want to tail the logs and then send that query. That way you will know exactly the error in detail

@User I used prisma to introspect the databases created by supertokens and it gives me this:

ts
model emailpassword_pswd_reset_tokens {
  user_id             String
  token               String              @unique
  token_expiry        Int
  emailpassword_users emailpassword_users @relation(fields: [user_id], references: [user_id])

  @@id([user_id, token])
  @@index([token_expiry], name: "emailpassword_password_reset_token_expiry_index")
}

model emailpassword_users {
  user_id                         String                            @id
  email                           String                            @unique
  password_hash                   String
  time_joined                     Int
  emailpassword_pswd_reset_tokens emailpassword_pswd_reset_tokens[]
}

model key_value {
  name            String  @id
  value           String?
  created_at_time Int?
}

model session_info {
  session_handle       String  @id
  user_id              String
  refresh_token_hash_2 String
  session_data         String?
  expires_at           Int
  created_at_time      Int
  jwt_user_payload     String?
}

That works fine. But then when I need to add my own models (user, posts, etc.) then I run the Prisma migration

It brings up problems afterwards

Hmmmmm

Perhaps prisma is changing the tables somehow

I suggest that you give a different db for supertokens entirely

And have one for your app that prisma can work with

Hmm okay so have them completely independent?

Yea. Ideally

That way, it will be easier for you to manage as well

So I will just have to maintain the ID one-to-one relation by myself manually

Like in this case we have emailpassword_users which contains the user ID, email, passhash

And I want another model called

User

which will have other things like bio, avatar, etc.

emailpassword_users

will be 1-1 with

User

Yea

They will have the same ID

So you create your own table which will have the extra user info

but in this case I will just manually keep track of that on my own (nothing code-wise will declare that relation)

What do u mean?